FlyingCam Is A Sweet DIY Webcam On A Stick

Imagine you want to monitor a pot on the stove to see if it’s boiling over for just a few minutes, but you don’t want to have a dedicated permanent IP webcam solution in your kitchen. [Sebastian Duell]’s FlyingCam hijacks an IKEA lamp gooseneck to become something you never knew you needed: a wireless camera for short-term random remote observation. It’s a beautiful combination of 3D printing and commercial device re-use, and when paired with his DIY wireless screen, it’s a complete solution.

The guts of this project aren’t critical, or expensive. It’s built around one of those ESP32 single-board webcams, with an added fan, battery pack, antenna, and a power switch. You turn it on, and the AP in the ESP32 fires up, or optionally connects to your network. Point the camera at your target and you’re set, at least if you want to sit by your computer. But [Sebastian] also designed a nice simple remote screen, so you can keep tabs on your spaghetti wherever you roam around the house.

We love the attention to keeping the design simple here, both in form and in function. It’s a one-task device, so it’s important that it be extremely easy to use, and it’s hard to beat just pointing the thing and turning on a switch. And it doesn’t hurt that it’s good looking to boot.

IKEA stuff is cheap and cheerful, but often it’s missing just that one functionality that we want. What good is an air-quality sensor without MQTT logging capability, for instance? Or a standing desk that can’t remember set heights? Get hacking!

Physical Computing Used To Be A Thing

In the early 2000s, the idea that you could write programs on microcontrollers that did things in the physical world, like run motors or light up LEDs, was kind of new. At the time, most people thought of coding as stuff that stayed on the screen, or in cyberspace. This idea of writing code for physical gadgets was uncommon enough that it had a buzzword of its own: “physical computing”.

You never hear much about “physical computing” these days, but that’s not because the concept went away. Rather, it’s probably because it’s almost become the norm. I realized this as Tom Nardi and I were talking on the podcast about a number of apparently different trends that all point in the same direction.

We started off talking about the early days of the Arduino revolution. Sure, folks have been building hobby projects with microcontrollers built in before Arduino, but the combination of a standardized board, a wide-ranging software library, and abundant examples to learn from brought embedded programming to a much wider audience. And particularly, it brought this to an audience of beginners who were not only blinking an LED for the first time, but maybe even taking their first steps into coding. For many, the Arduino hello world was their coding hello world as well. These folks are “physical computing” natives.

Now, it’s to the point that when Arya goes to visit FOSDEM, an open-source software convention, there is hardware everywhere. Why? Because many successful software projects support open hardware, and many others run on it. People port their favorite programming languages to microcontroller platforms, and as they become more powerful, the lines between the “big” computers and the “micro” ones starts to blur.

And I think this is awesome. For one, it’s somehow more rewarding, when you’re just starting to learn to code, to see the letters you type cause something in the physical world to happen, even if it’s just blinking an LED. At the same time, everything has a microcontroller in it these days, and hacking on these devices is also another flavor of physical computing – there’s code in everything that you might think of as hardware. And with open licenses, everything being under version control, and more openness in open hardware than we’ve ever seen before, the open-source hardware world reflects the open-source software ethos.

Are we getting past the point where the hardware / software distinction is even worth making? And was “physical computing” just the buzzword for the final stages of blurring out those lines?

Hackaday Europe 2025 Welcomes David Cuartielles, Announces Friday Night Bring-a-Hack

If you’re coming to Hackaday Europe 2025, you’ve got just over a week to get your bags packed and head on out to Berlin. Of course you have tickets already, right? And if you were still on the fence, let us tempt you with our keynote talk and some news about the Friday night meetup, sponsored by Crowd Supply.

Continue reading “Hackaday Europe 2025 Welcomes David Cuartielles, Announces Friday Night Bring-a-Hack”

Practice While You Work

This week, I had to do something I haven’t done in a long, long time: make myself a custom PCB the old-fashioned way, with laser toner and etchant. The reason? I bought a horrible K40 laser cutter, and the motion controller doesn’t seem to be able to do acceleration control, which means the machine rams full speed into and out of 90 degree corners, for instance. It sounds awful, and it dramatically limits how fast the laser cutter can run.

The plan, then, is to use a controller based on the wonderful FluidNC, but that meant making an adapter board for the flat-flex cable that connects to the X carriage, and the connector has 2 mm pin spacings instead of the usual 2.54 mm, and it just doesn’t fit into any prototyping boards that I have lying around. Besides, a custom PCB adapter board just looks neater.

I wasn’t confident that I could align and drill the dozen small holes for the flat-flex connector; they didn’t have much extra space around them for the copper pads. These holes had to be dead on, or risk ripping them up. And this is where I heard the voice of my old Jedi master.

When you have a tricky operation coming up that requires more precision than you’re immediately comfortable with, you can practice on the other parts of the project that don’t demand that much precision. Pretending that they do, and taking all the care that you can, gets you in shape to tackle the truly critical bits, and if you mess up a little on the easy stuff, it’s not a problem. I had more than a few pin-headers and other random holes to drill for practice anyway.

Now of course, you could always be giving all of your projects 100% all of the time, if time is never of the essence and effort is free. In the real world, you don’t always want to work at maximum precision. Good enough is often good enough.

But there’s also a time and a place for practicing precision, especially when you see a need for it up ahead. Drilling the big holes dead center got me back in the swing of things, and they needed to get drilled one way or the other. I find it useful to think about the job first, plan ahead where the tricky bits are going to be, and then treat the “easy” stuff along the way as practice for the more demanding operations. Hope you do too!

Hackaday Europe 2025: Workshops And More Speakers

We’re proud to announce the last round of speakers, as well as the two workshops that we’ll be running at 2025 Hackaday Europe in Berlin on March 15th and 16th — and Friday night the 14th, if you’re already in town.

The last two years that we’ve done Hackaday Europe in Berlin have been awesome, and this year promises to keep up the tradition. We can’t wait to get our hands on the crazy selection of SAO badge addons that are going to be in each and every schwag bag.

Tickets for the event itself are going fast, but the workshop tickets that go on sale at 8:00 AM PST sell out even faster. And you need the one to enjoy the other, so get your tickets now!

Continue reading “Hackaday Europe 2025: Workshops And More Speakers”

We’re Hiring: Come Join Us!

You wake up in the morning, and check Hackaday over breakfast. Then it’s off to work or school, where you’ve already had to explain the Jolly Wrencher to your shoulder-surfing colleagues. And then to a hackspace or back to your home lab, stopping by the skull-and-cross-wrenches while commuting, naturally. You don’t bleed red, but rather #F3BF10. It’s time we talked.

The Hackaday writing crew goes to great lengths to cover all that is interesting to engineers and enthusiasts. We find ourselves stretched a bit thin and it’s time to ask for help. Want to lend a hand while making some extra dough to plow back into your projects? We’re looking for contributors to write a few articles per week and keep the Hackaday flame burning.

Contributors are hired as private contractors and paid for each article. You should have the technical expertise to understand the projects you write about, and a passion for the wide range of topics we feature. You’ll have access to the Hackaday Tips Line, and we count on your judgement to help us find the juicy nuggets that you’d want to share with your hacker friends.

If you’re interested, please email our jobs line (jobs at hackaday dot com) and include:

  • One example article written in the voice of Hackaday. Include a banner image, between 150 and 300 words, the link to the project, and any in-links to related and relevant Hackaday features. We need to know that you can write.
  • Details about your background (education, employment, interests) that make you a valuable addition to the team. What do you like, and what do you do?
  • Links to your blog/project posts/etc. that have been published on the Internet, if any.

Questions? Don’t hesitate to ask below. Ladies and Gentlemen, start your applications!

LCD Stackup Repair: Not For The Faint Of Heart

Coming straight to the point: [Ron Hinton] is significantly braver than we are. Or maybe he was just in a worse situation. His historic Acer K385s laptop suffered what we learned is called vinegar syndrome, which is a breakdown in the polarizers that make the LCD work. So he bit the bullet and decided to open up the LCD stack and replace what he could.

Nothing says “no user serviceable parts inside” quite like those foil-and-glue sealed packages, but that didn’t stop [Ron]. Razor blades, patience, and an eye ever watchful for the connectors that are seemingly everywhere, and absolutely critical, got the screen disassembled. Installation of the new polarizers was similarly fiddly.

In the end, it looks like the showstopper to getting a perfect result is that technology has moved on, and these older screens apparently used a phase correction layer between the polarizers, which might be difficult to source these days. (Anyone have more detail on that? We looked around and came up empty.)

This laptop may not be in the pantheon of holy-grail retrocomputers, but that’s exactly what makes it a good candidate for practicing such tricky repair work, and the result is a readable LCD screen on an otherwise broken old laptop, so that counts as a win in our book.

If you want to see an even more adventurous repair effort that ended in glorious failure, check out [Jan Mrázek]’s hack where he tries to convert a color LCD screen to monochrome, inclusive of scraping off the liquid crystals! You learn a lot by taking things apart, of course, but you learn even more by building it up from first principles. If you haven’t seen [Ben Krasnow]’s series on a completely DIY LCD screen, ITO-sputtering and all, then you’ve got some quality video time ahead of you.