USB Power Bank’s Auto-Off Becomes Useful Feature In Garage Door Remote

For devices that are destined for momentary and infrequent use as well as battery power, some kind of power saving is pretty much a required feature. For example, when [PJ Allen] turned two ESP8266-based NodeMCU development boards into a replacement wireless remote garage door opener, a handy USB power bank ended up serving as a bit of a cheat when migrating the remote away from the workbench. Instead of moving the board from USB to battery power and implementing some kind of sleep mode or auto-off, [PJ Allen] simply plugged in a USB power bank and let it do all the work.

This is how the feature works: some USB power banks turn themselves off unless they detect a meaningful current draw. That means that if the power bank is charging a phone, it stays on, but if it’s only lighting up a few LEDs, it’ll turn itself off. This feature can be a frustrating one, but [PJ Allen] realized that it could actually be useful for a device like his garage door remote. Turning on the power bank delivers 5 V to the NodeMCU board and allows it to work, but after about fifteen seconds, the power bank turns itself off. Sure, strapping a power bank to the remote makes the whole thing bigger than it needs to be, but it’s a pretty clever use of the minimum load as an effortless auto-off feature.

The NodeMCU boards in [PJ Allen]’s DIY remote use ESP-NOW for their wireless communications, a nifty connectionless protocol from Espressif that we’ve seen used in other projects as well, such as this ESP32-based walkie-talkie.

A New Spin On Empty Filament Spools For Part Storage

Empty spools from 3D printer filament are the kind of thing that begs to be repurposed, and one option is [3d-printy]’s vertical filament spool parts drawer design. The way this solution works is by using the spool to hold twelve vaguely pie-shaped drawers that can be individually unlocked and removed entirely, which makes accessing their contents (or dumping them out) much easier. This method requires the spools to be oriented vertically, so it ends up handling a bit like a Rolodex.

One downside of the design is that it requires two inserts to be installed on the inside of the spool walls, which act as guide rails and lock points for the drawers. Another is that managing a vertical spool can be a bit awkward, given its lack of flat surfaces. Happily, there is an option for a matching stand that not only provides a flat base, but keeps any accidentally-unlocked drawers from falling out and spilling their contents.

The project files are OpenSCAD files, which allows easy customization for different spool manufacturers and dimensions, and [3d-printy] provides measurements for some common ones. Another nice element of this design is that no single part uses more than 30 grams of filament, which makes printing them an attractive way to use up the last bits of filament rolls.

We’ve seen drawer-style storage for filament spools before, but haven’t seen a design quite like this one before. Watch an overview of the drawer design as well as the spool holders in the videos, embedded below.

Continue reading “A New Spin On Empty Filament Spools For Part Storage”

Hacking A Thermal Imager For Dual-use Of The Thermal Sensor

Sometimes a device doesn’t do quite what one needs, and in those cases a bit of tampering might do the trick. That’s what led to being able to record video from a HTI HT-A1 thermal imager despite the device not actually supporting that function, thanks to careful investigation and warranty violation.

Plugging in a custom USB cable allows a mobile phone app to access the thermal sensor, while the host device itself remains ignorant.

We’ve seen a teardown of the HT-A1 in the past, and it turns out that Seek — the manufacturer for the actual thermal sensor inside the device — released an OEM development kit and mobile phone app for their modules. Could this mean that the raw sensor module in the HT-A1 could be accessed via the developer kit app? One hacked together USB cable later showed that the answer is yes! Not only does the app allow viewing thermal imagery, but it makes it possible to do things like record video (a function the HT-A1 itself does not support.)

But even if the HT-A1 doesn’t allow recording, as a handheld thermal sensor with a screen it’s still pretty useful in its own way and it would be shame to gut the unit just for a raw sensor module. The best solution ended up being to put the sensor back into the HT-A1, and install some switching circuitry to disconnect the sensor from the HT-A1’s CPU and divert its data to the USB plug on demand. This means the HT-A1 can be used normally, but by plugging in a custom-made cable while the unit is off, the thermal sensor can be accessed by the mobile phone app instead. Best of both worlds. You can see a brief celebratory thermal cat video embedded below, proving it works.

Continue reading “Hacking A Thermal Imager For Dual-use Of The Thermal Sensor”

Robotic Ball-Bouncing Platform Learns New Tricks

[T-Kuhn]’s Octo-Bouncer platform has learned some new tricks since we saw it last. If you haven’t seen it before, this device uses computer vision from a camera mounted underneath its thick, clear acrylic platform to track a ball in 3D space, and make the necessary (and minute) adjustments needed to control the ball’s movements with a robotic platform in real time.

We loved the Octo-Bouncer’s mesmerizing action when we saw it last, and it’s only gotten better. Not only is there a whole new custom ball detection algorithm that [T-Kuhn] explains in detail, there are also now visualizations of both the ball’s position as well as the plate movements. There’s still one small mystery, however. Every now and again, [T-Kuhn] says that the ball will bounce in an unexpected direction. It doesn’t seem to be a bug related to the platform itself, but [T-Kuhn] has a suspicion. Since contact between the ball and platform is where all the control comes from, and the ball and platform touch only very little during a bounce, it’s possible that bits of dust (or perhaps even tiny imperfections on the ball’s surface itself) might be to blame. Regardless, it doesn’t detract from the device’s mesmerizing performance.

Design files and source code are available on the project’s GitHub repository for those who’d like a closer look. It’s pretty trippy watching the demonstration video because there is so much going on at once; you can check it out just below the page break.

Continue reading “Robotic Ball-Bouncing Platform Learns New Tricks”

Just How Did 1500 Bytes Become The MTU Of The Internet?

[Benjojo] got interested in where the magic number of 1,500 bytes came from, and shared some background on just how and why it seems to have come to be. In a nutshell, the maximum transmission unit (MTU) limits the maximum amount of data that can be transmitted in a single network-layer transaction, but 1,500 is kind of a strange number in binary. For the average Internet user, this under the hood stuff doesn’t really affect one’s ability to send data, but it has an impact from a network management point of view. Just where did this number come from, and why does it matter?

[Benjojo] looks at a year’s worth of data from a major Internet traffic exchange and shows, with the help of several graphs, that being stuck with a 1,500 byte MTU upper limit has real impact on modern network efficiency and bandwidth usage, because bandwidth spent on packet headers adds up rapidly when roughly 20% of all packets are topping out the 1,500 byte limit. Naturally, solutions exist to improve this situation, but elegant and effective solutions to the Internet’s legacy problems tend to require instant buy-in and cooperation from everyone at once, meaning they end up going in the general direction of nowhere.

So where did 1,500 bytes come from? It appears that it is a legacy value originally derived from a combination of hardware limits and a need to choose a value that would play well on shared network segments, without causing too much transmission latency when busy and not bringing too much header overhead. But the picture is not entirely complete, and [Benjojo] asks that if you have any additional knowledge or insight about the 1,500 bytes decision, please share it because manuals, mailing list archives, and other context from that time is either disappearing fast or already entirely gone.

Knowledge fading from record and memory is absolutely a thing that happens, but occasionally things get saved instead of vanishing into the shadows. That’s how we got IGNITION! An Informal History of Liquid Rocket Propellants, which contains knowledge and history that would otherwise have simply disappeared.

We All Need A Win Sometimes, So Make Them Yourself

We all need the occasional win when it comes to work or personal projects. Being able to feel that payoff of progress and satisfaction is deeply important, because if everything is always uphill, that’s a recipe for burnout. Avoiding that is important enough to explore how to set oneself up for a few easy wins.

Getting the occasional win helps us stay motivated, creative, and fulfilled. Meaningful work can deliver on this, but many of us rely on hobbies to make up any shortfall. Sometimes, that isn’t enough. Hobbies themselves can end up feeling like a chore, and when that happens, they cease to provide respite. The good news is that I believe it is possible to exploit the benefits of hobbies to deliver supplemental “wins” when they are needed most, and I’ll explain how.

I have found that successes do not have to be hard-won in order to be beneficial, but they do need to be relevant to one’s passions and interests. So, when naturally-occurring successes come too few and far between, and hobbies aren’t doing the trick, use knowledge of yourself to stack the deck for some easy wins. It can tip the scales towards feeling meaningful progress and fulfillment in the face of what could otherwise lead to burnout. Continue reading “We All Need A Win Sometimes, So Make Them Yourself”

Video De-shaker Software Measures Linear Rail Quality

Here’s an interesting experiment that attempts to measure the quality of a linear rail by using a form of visual odometry, accomplished by mounting a camera on the rail and analyzing the video with open-source software usually used to stabilize shaky video footage. No linear rail is perfect, and it should be possible to measure the degree of imperfection by recording video footage while the camera moves down the length of the rail, and analyzing the result. Imperfections in the rail should cause the video to sway a proportional amount, which would allow one to characterize the rail’s quality.

To test this idea, [Saulius] attached a high-definition camera to a linear rail, pointed the camera towards a high-contrast textured pattern (making the resulting video easier to analyze), and recorded video while moving the camera across the rail at a fixed speed. The resulting video gets fed into the Deshaker plugin for VirtualDub, of which the important part is the deshaker.log file, which contains X, Y, rotate, and zoom correction values required to stabilize the video. [Saulius] used these values to create a graph characterizing the linear rail’s quality.

It’s a clever proof of concept, especially in how it uses no special tools and leverages a video stabilizing algorithm in an unusual way. However, the results aren’t exactly easy to turn into concrete, real-world measurements. Turning image results into micrometers is a matter of counting pixels, and for this task video stabilizing is an imperfect tool, since the algorithm prioritizes visual results instead of absolute measurements. Still, it’s an interesting experiment, and perfectly capable of measuring rail quality in a relative sense. Can’t help but be a bit curious about how it would profile something like these cardboard CNC modules.