The ever-shrinking size of electronics and sensors has allowed wearables to help us quantify more and more about ourselves in smaller and smaller packages, but one major constraint is the size of the battery you can fit inside. What if you could remotely power a wearable device instead?

Researchers at Carnegie Mellon University were able to develop a power transmitter that lets power flow over human skin to remote devices over distances as far a head-to-toe. The human body can efficiently transmit 40 MHz RF energy along the skin and keeps this energy confined around the body and through clothing, as the effect is capacitive.

The researchers were able to develop several proof-of-concept devices including “a Bluetooth
ring with a joystick, a stick-and-forget medical patch which logs data, and a sun-exposure patch with a screen — demonstrating user input, displays, sensing, and wireless communication.” As the researchers state in the paper, this could open up some really interesting new wearable applications that weren’t possible previously because of power constraints.

If you’re ready to dive into the world of wearables, how about this hackable smart ring or a wearable that rides rails?

A quick look around at any coffee shop, city sidewalk, or sadly, even at a traffic light will tell you that people are on their phones a lot. But exactly how much is that? For Americans in 2023, it was a mind-boggling 100 trillion megabytes, according to the wireless industry lobbying association CTIA. The group doesn’t discuss their methodology in the press release, so it’s a little hard to make judgments on that number’s veracity, or the other numbers they bandy about, such as the 80% increase in data usage since 2021, or the fact that 40% of data is now going over 5G connections. Some of the numbers are more than a little questionable, too, such as the claim that 330 million Americans (out of a current estimate of 345.8 million people) are covered by one or more 5G networks. Even if you figure that most 5G installations are in densely populated urban areas, 95% coverage seems implausible given that in 2020, 57.5 million people lived in rural areas of the USA. Regardless of the details, it remains that our networks are positively humming with data, and keeping things running is no mean feat.

If you’ve ever wondered what one does with a degree in wildlife biology, look no further than a study that looks into “avian-caused ignitions” of wildfires. The study was led by Taylor Barnes, a wildlife biologist and GIS specialist who works for a civil engineering firm, and concludes that some utility poles are 5 to 8 times more likely to spark a wildfire than the average pole due to “thermal events” following electrocution of a bird, squirrel, bear, or idiot. Unfortunately, the paper is paywalled, so there’s no information on methodology, but we’re guessing a grad student or intern spent a summer collecting animal carcasses from beneath power poles. It’s actually very valuable work since it informs decisions on where to direct wildlife mitigation efforts that potentially reduce the number of service outages and wildfires, but it’s still kinda funny.

From the “How to get rid of a lot of money in a hurry” files comes a story of a bad GPU made into an incredibly unattractive purse. About the only thing good about the offering, which consists of a GeForce GT 730 video card stuffed into a clear plastic box with a gold(ish) chain attached, is the price of $1,024. The completely un-dodgy GPUStore Shopify site also lists a purse fashioned from an NVIDIA H100 Tensor Core GPU for a cool $65,536. At least somebody knows about base two.

And finally, if you’ve struggled with the question of what humanoid robots bring to the table, chances are pretty good that adding the ability to fly with four jet engines isn’t going to make things much clearer. But for some reason, a group from the Italian Institute of Technology is working on the problem of “aerial humanoid robotics” with a cherub-faced bot dubbed iRonCub. The diminutive robot is only about 70 kilograms, which includes the four jet engines generating a total of 1,000 newtons of thrust. Applications for the flying baby robot are mostly left to the imagination, although there is a vague reference to “search and rescue” applications; we’re not sure about you, but if we’re lost in the woods and half-crazed from hunger and exposure, a baby descending from the sky on a 600° plume of exhaust might not be the most comforting sight.

Every now and then, a commercial product aims to help you in your life journey, in a novel way, making your life better through its presence. Over the years, I’ve been disappointed by such products far more often than I have been reassured, seeing each one of them rendered unimaginative and purposeless sometimes even despite the creator’s best intentions. The pressures of a commercial market will choke you out without remorse, metal fingers firmly placed on your neck, tightening with every move that doesn’t promise profit, and letting money cloud your project’s vision. I believe that real answers can only come from within hacker communities, and as we explore, you might come to see it the same way.

This is the tip of the iceberg of a decade-long project that I hope to demonstrate in a year or two. I’d like to start talking about that project now, since it’s pretty extensive; the overall goal is about using computers to help with human condition, on a personal level. There’s a lot of talk about computers integrating into our lives – even more if you dare consult old sci-fi, much of my inspiration.

Tackling a gigantic problem often means cutting it down into smaller chunks, though, so here’s a small sub-problem I’ve been working on, for years now, on and off: Can you use computers to modify your sense of time?

The Time Question

Ever start your day thinking you will hack on a project, and in the evening, realize you’ve instead done something else entirely? Sometimes you find something cool while distracted, and sometimes, getting distracted comes to haunt you.

This has been a staple of my days as long as I remember my conscious life, and at some point, I started wondering just how much this could be modified. Do you remember one particular project we’ve seen a couple people build, a vibration-based compass build that gives you a sense of where north is? Ironically, I have made PCBs for building my own version of this project – they were designed in 2022, I finally ordered them last year in 2023, and I haven’t gotten to assemble them still.

So, you can give yourself a sense of “where’s north” – something that humans are missing, generally. Technically, humans are also missing a source of time, which is why we always supplemented it with wrist-worn watches and pocket clocks. Having compared my day plans to what actually happens on that day for two decades, I can see that I need something more than that. It’s traditionally been common for me to mis-estimate when exactly I could get something done – I would give an estimate that felt correct, then start doing part of the task and forget about the flow of time, minutes passing by me.

So, there are two problems here. One of them is that, despite having been alive for a fair bit of time, my database of “how much it takes for me to do X” is inaccurate. This makes sense: keeping such references is a conscious effort that might not extend to, and day-to-day situations are highly variable. Still, if someone is relying on me, it would be nice to be aware enough to at least notify that person, and to learn to plan ahead. Another is that it’s easy for me to get and forget about the flow of time. It sure helps me concentrate on articles, but it doesn’t help when someone is waiting on me.

At some point, this started to screw with my sense of self. Really, just how much can you rely on some aspects of your mind if it continuously fails you and people you care about, in a manner that you are expected to “just figure out already”? You have to learn to distrust certain basic aspects of your cognitive processes; again and again, something as “simple” as time planning is weighted down by all the instance of letting people down with zero intention to do so. This is a pretty uncomfortable position to be in, if being honest with yourself is a priority of yours. Unsurprisingly, it also made things pretty difficult when talking about employment or real-life obligations. Something had to be done.

Well, could you give yourself a sense of time, say, with vibromotors? Apparently, you can, but there’s nuance to it. Let me tell you about two projects I’ve built to attempt this, and some basic concepts I learned about human-computer integration.

The Not-A-Bomb Wearable

My first project in this vein grew out of a purpose-less experiment, funnily enough: a project literally called I Made This And I Don’t Know Why – a simple board I built to make use of seven-segment displays our hackerspace had a dozen of. ESP8266, dynamic indication with a shift register, and MicroPython – writing firmware for this board was a nice challenge in writing non-blocking code and finding portions of code to optimize. Soon, the board found a good few purposes – among them, a time tracker.

I decided to solve a simple problem – building a mental database on the amount of time does it take me to get from “start” to “finish” for an arbitrary task. Tracking that was tricky – say, I want to check the length of a bicycle ride from my house to a certain point. I’d need to check my phone at the exact time when I left the house, keep that time in mind, and then, once I’ve arrived to my destination, check again. Both of these require some time to execute and some memory, so, I decided to make an automatic countdown timer. Glancing at my wrist felt significantly easier, so, after some cutting, sewing, and hotglue work, I made one of the IMTAIDKW boards into an oversized watch, and used one of my universal power source designs to power it from a 18650.

There were some setbacks during – notably, this countdown timer required me to patch MicroPython’s ESP8266 port, due to an obscure bug making the time.time() function seriously imprecise; an inaccurate countdown timer wasn’t in my plan. Still, it was a nice experiment – relying on something that you build yourself is always fun, and I’ve added features like adjusting the start time. It was also automatic enough to be useful, with digits large enough and bright enough to be noticeable, still, making for an unobtrusive device, and pretty cool to wear.

The main problem was that I forgot to put it on and start the countdown. It was a purpose-built device, and I only needed it a couple times a day at its very most, so most of the time it stayed off my wrist, and I would even lose track of it sometimes. Another problem was remembering to check the time of arrival, unsurprisingly – looking at my wrist was easy enough, so most of the time I could notice the time difference and go “oh interesting”, but even then, it was easy to forget. The last, main problem, was actually keeping a mental database – turns out that when you need to remember pretty similar datapoints, it’s easy to confuse them. Does it normally take me 15 minutes to get to the city center, or was it the electronics store? This turned out to be pretty easy to mix up.

The lessons from this iteration: decreasing resistance to use is good, collecting data is good, and, you should automate the data collection process if at all possible. I wouldn’t stop here, of course – some time later, I found an even nicer wristband to hack on.

Unconventional Battery Upgrades

The TTGO (or was it Lilygo?) T-Wristband is a fun product – with an ESP32 at its heart, a good few sensors, a 160 x 80 IPS LCD, and a single capacitive button. It’s an old device by now, but when I bought it in the beginning of 2020, it was fun to hack on, and hack it I did, making it run MicroPython. I didn’t know what exactly to do with it, but soon I remembered about the “sense of time” project. At the time, I wanted to tap into my life minute-by-minute and see if I could build a device able to help me notice when I’m distracted. The minimum viable prototype idea was very simple – adding a vibromotor to the watch, then having it vibrate exactly every minute, having it be an “am I currently spending my time correctly” reminder.

The problem was, by the time I came up with that, a good few months passed where the wristband was sitting in a drawer with the battery fully discharged – hurting its capacity a bit, which, at 80 mAh, was already not great. Also, I wanted to be able to keep adding features to the code without carefully balancing sleep modes or having to charge my watch multiple times throughout the day; I just wanted to run code and charge the battery every night at most. So, it got a battery upgrade – a Samsung phone battery glued to, ahem, yet another wristband, and a devboard with vibromotor driver taped on top. After the hardware tweaks, the code itself was seriously easy to write.

Whenever I’d notice it vibrating, I’d ask myself – “am I doing the right thing right now?” And, to my surprise, it did catch some distraction moments every now and then, for sure!  Oftentimes, I wasn’t doing the right thing, in one way or another, and a reminder about being supposed to do something else was quite welcome. Other times, when I was focused on something, the “am I doing the right thing” question would get a “yes” in my mind, and, it felt good to think that.

It wasn’t as comfortable in times when I wasn’t expecting me to be on top of things – while I’d be resting, the every-minute feedback of the watch would feel annoying and needlessly distracting; soon, I implemented a vibration toggle with the capacitive button, and a few other things. My guess is that the annoyance factor and generally getting used to the vibrations has made me less sensitive to the vibromotor’s signal, which in turn made the wearable less effective at its goal. Apart from that, the battery wire kept breaking every so often, taking the watch out of commission, which made it hard to start properly relying on it.

On the upside – it turned out that this idea has been floating in collective unconscious for a while now, to the point that it was the point of a watch worn by one of the characters in Mr. Robot, and a relatable one at that. It’s pretty good to get external independent confirmation that an idea of yours has merit! In particular, the video above reminds me a lot of my experiences – I spent less time on my phone and generally less time doing things I didn’t want to do, I was getting up and walking around more often, and, I had add a small feature that mutes the watch when I go to sleep.

It All Worked Out Despite The Plan

Lessons here? If you can hook your device’s signals into producing a thought in your brain, that helps massively – checking for “am I doing the right thing” every minute came to me naturally, and a lot quicker than I expected it to. Context sensitivity is a must for self-help devices- the wearable would’ve had been way more effective if I had some ways to detect that I’m likely to be distracted, as opposed to having it vibrate indiscriminately every minute. In general, make sure your device is not annoying to you in any bad way – it’s supposed to be helping you, so any reason you’re annoyed by it, is a problem for the device’s primary usefulness.

On the hardware side, make your device reliable – building habits takes an ongoing effort, and you want it to be consistent. At the same time, consider building your device as a playground for developing your idea further; this could require a bigger battery, or more space inside the case, or an expansion socket. Reality is to plans what pure oxygen is to paper, and getting things done is typically way more important than getting them right the first time. Last but by no means least, wires suck – I’ve been saying this, and I will repeat that as much as needed.

In the end, I have mostly solved my original problem by tweaking my personal approach to time over the years, learning to over-estimate estimates, and ultimately putting myself in less situation where I am under time pressure – it turned out that was the bigger problem. It would’ve been nice if I could’ve noticed that sooner, but, the devices I’ve built certainly have helped. Today, I still have some sense-of-time solutions I rely on, but they are new, designed with these lessons in mind, and they’re a part of a multi-faceted system that I can only tell you about in the next articles – stay tuned!

[mitxela] has a tiny problem, literally: some of his projects are so small as to defy easy programming. While most of us would probably solve the problem of having no physical space on a board to mount a connector with WiFi or Bluetooth, he took a different path and gave this clever light-based programming interface a go.

Part of the impetus for this approach comes from some of the LED-centric projects [mitxela] has tackled lately, particularly wearables such as his LED matrix earrings or these blinky industrial piercings. Since LEDs can serve as light sensors, albeit imperfect ones, he explored exactly how to make the scheme work.

For initial experiments he wisely chose his larger but still diminutive LED matrix badge, which sports a CH32V003 microcontroller, an 8×8 array of SMD LEDs, and not much else. The video below is a brief summary of the effort, while the link above provides a much more detailed account of the proceedings, which involved a couple of false starts and a lot of prototyping that eventually led to dividing the matrix in two and ganging all the LEDs in each half into separate sensors. This allows [mitxela] to connect each side of the array to the two inputs of an op-amp built into the CH32V003, making a differential sensor that’s less prone to interference from room light. A smartphone app alternately flashes two rectangles on and off with the matrix lying directly on the screen to send data to the badge — at a low bitrate, to be sure, but it’s more than enough to program the badge in a reasonable amount of time.

We find this to be an extremely clever way to leverage what’s already available and make a project even better than it was. Here’s hoping it spurs new and even smaller LED projects in the future.

You might think Google Glass was an innovative idea, but [Allison Marsh] points out that artist [Lisa Krohn] imagined the Cyberdesk in 1993. Despite having desk in the name, the imagined prototype was really a wearable computer. Of course, in 1993, the technology wasn’t there to actually build it, but it does look like [Krohn] predicted headgear that would augment your experience.

Unlike Google Glass, the Cyberdesk was worn like a necklace. There are five disk-like parts that form a four-key keyboard and something akin to a trackpad. There were two models built, but since they were nonfunctional, they could have any imagined feature you might like. For example, the system was supposed to draw power from the sun and your body, something practical devices today don’t really do, either.

She also imagined a wrist-mounted computer with satellite navigation, a phone, and more. Then again, so did [Chester Gould] when he created Dick Tracy. The post also talks about a more modern reimagining of the Cyberdesk last year.

While this wasn’t a practical device, it is a great example of how people imagine the future. Sometimes, they miss the mark, but even then, speculative art and fiction can serve as goals for scientists and engineers who build the actual devices of the future.

We usually think about machines augmenting our intelligence and senses, but maybe we should consider more physical augmentation. We do appreciate seeing designs that are both artistic and functional.

Soldering is easy, as long as you have one hand to hold the iron, one to hold the solder, and another to hold the workpiece. For those of us not so equipped, there’s the new and improved Solder Sustainer v2, which aims to free up one of however many hands you happen to have.

Eagle-eyed readers will probably recall an earlier version of Solder Sustainer, which made an appearance in last year’s Hackaday Prize in the “Gearing Up” round. At the time we wrote that it looked a bit like “the love child of a MIG welder and a tattoo machine.” This time around, [RoboticWorx] has rethought that concept and mounted the solder feeder on the back of a fingerless glove. The solder guide is a tube that clips to the user’s forefinger, which makes much finer control of where the solder meets the iron possible than with the previous version. The soldering iron itself is also no longer built into the tool, giving better control of the tip and letting you use your favorite iron, which itself is no small benefit.

Hats off to [RoboticWorx] for going back to the drawing board on this one. It isn’t easy to throw out most of your design and start over, but sometimes it just makes sense.

Regular 2D sewing of anything is inherently wasteful. You can align the pattern pieces however you want, but there’s going to be wasted everything — thread, fabric, and interfacing — whether you get it right the first time or not. Never mind the fact that people tend to create a muslin (prototype) first using inexpensive fabric (like muslin) for the purposes of getting the fit right.

The MIT Self-Assembly Lab x Ministry of Supply have come up with a 4D garment construction technique that minimizes waste while being pretty darn cool at the same time. They’ve created a knit dress that combines several techniques and tools, including heat-activated yarns, computerized knitting, and 6-axis robotic activation. The result is a dress that can be permanently molded to fit the body however and wherever you want, using a heat gun mounted on a 6-axis robotic arm.

As far as we can tell, a finished dress does not come off of the machine in the short demo video after the break. It looks like it still has to be sewn together, which creates some potential for waste, but absolutely nothing like conventional methods.

This is probably the coolest dress we’ve seen since the one covered in LCD panels.