Are you still writing notes on paper and sticking them to the fridge like it’s the ’80s? Well, if you are, and you read this site, you’d probably like to upgrade to something a bit more 21st century. And, thanks to robot maker [James Bruton], you can leave your old, last century, message taking behind as he has a tutorial up showing you how to build an internet connected e-paper message display board. And, if you have a Raspberry Pi, an e-paper display and adapters just lying around doing nothing, then this project will cost you less than the buck that paper and a magnet will cost you.
Sarcasm aside, this is a pretty nice project. As mentioned, the base of this is a Raspberry Pi – [James] uses a Pi 4, but you could get away with an older, lower powered model as well. This powers the cheap(-ish) e-paper display he found online, which comes with the necessary adapters for the Pi, as well as a python library to write to the display. [James] uses a Google Sheet as the cloud storage for the message board, and there is some python code to access the cells in the Sheet and print them on the display if anything has changed. A cron job runs the script every 5 minutes to catch changes in the messages.
As with most of the projects that [James] does, he gives a good overview in the video and goes over the process of finding the hardware and writing and updating the script. He’s put the script and details as well as the CAD file for the frame he created for the project up on GitHub. [James] has been featured several times on the site before, check out some of his projects.
Amateur radio operators and shortwave listeners have a common enemy: QRM, which is ham-speak for radio frequency interference caused by man-made sources. Indiscriminate, often broadband in nature, and annoying as hell, QRM spews forth from all kinds of sources, and can be difficult to locate and fix.
But [Emilio Ruiz], an operator from Mexico, got a little help from Mother Nature recently in his quest to lower his noise floor. Having suffered from a really annoying blast of RFI across wide swaths of the radio spectrum for months, a summer thunderstorm delivered a blessing in disguise: a power outage. Hooking his rig up to a battery — all good operators are ready to switch to battery power at a moment’s notice — he was greeted by blessed relief from all that noise. Whatever had caused the problem was obviously now offline.
Rather than waste the quiet time on searching down the culprit, [Emilio] worked the bands until the power returned, and with it the noise. He killed the main breaker in the house and found that the noise abated, leading him on a search of the premises with a portable shortwave receiver. The culprit? Unsurprisingly, it was a cheap laptop power supply. [Emilio] found that the switch-mode brick was spewing RFI over a 200-meter radius; a dissection revealed that the “ferrite beads” intended to suppress RFI emissions were in fact just molded plastic fakes, and that the cord they supposedly protected was completely unshielded.
We applaud [Emilio]’s sleuthing for the inspiration it gives to hunt down our own noise-floor raising sources. It kind of reminds us of a similar effort by [Josh (KI6NAZ)] a while back.
Very often, particularly on the Internet, we’re fooled into thinking bigger is always better. The fact remains that this isn’t always the case. When it comes to reflow ovens, for example if you’re working with short runs of small PCBs, or if you just don’t have a lot of space in the workshop, a smaller oven will be more desirable than a large one. It’s factors like these that drove [Sergi Martínez]’s latest build.
Built inside a metal project case, first attempts involved using an off-the-shelf heating element, with poor results. The element had a high thermal inertia, and was designed for use in water, so didn’t last in the reflow application. Learning from the experience of others, [Sergi] switched to using halogen lamps, netting much greater success. An Arduino Nano is responsible for running the show, using firmware developed by [0xPIT]. There’s also a screen for monitoring reflow profiles, and a cooling fan to help keep temperature in the ideal zone.
It’s a tidy build that would be particularly useful for quickly running batches of small PCBs without the long wait times required to heat a larger oven. Energy efficiency should be better, too. Of course, if you’re a fan of the classic toaster oven builds, we’ve got those too. Video after the break.
Good news, Fusion 360 fans — Autodesk just announced that they won’t be removing support for STEP file exports for personal use licensees of the popular CAD/CAM platform after all.
As we noted last week, Autodesk had announced major changes to the free-to-use license for Fusion 360. Most of the changes, like the elimination of simulations, rolling back of some CAM features, and removal of generative design tools didn’t amount to major workflow disruptions for many hobbyists who have embraced the platform. But the loss of certain export formats, most notably STEP files, was a bone of contention and the topic of heated discussion in the makerverse. Autodesk summed up the situation succinctly in their announcement, stating that the reversal was due to “unintended consequences for the hobbyist community.”
While this is great news, bear in mind that the other changes to the personal use license are still scheduled to go into effect on October 1, while the planned change to limit the number of active projects will go into effect in January 2021. So while Fusion 360 personal use licensees will still have STEP files, the loss of other export file formats like IGES and SAT are still planned.
People making DIY controls to enhance flight simulators is a vibrant niche of engineering and hackery, and it sure looks like Microsoft Flight Simulator is doing its part to keep the scene lively. [Akaki Kuumeri]’s latest project turns an Xbox One gamepad into a throttle-and-stick combo that consists entirely of 3D printed parts that snap together without a screw in sight. Bummed out by sold-out joysticks, or just curious? The slick-looking HOTAS (hands on throttle and stick) assembly is only a 3D printer and an afternoon away. There’s even a provision to add elastic to increase spring tension if desired.
The design looks great, and the linkages in particular look very well thought-out. Ball and socket joints smoothly transfer motion from one joystick to the other, and [Akaki] says the linkages accurately transmit motion with very little slop.
There is a video to go with the design (YouTube link, embedded below) and it may seem like it’s wrapping up near the 9 minute mark, but do not stop watching because that’s when [Akaki] begins to go into hacker-salient details about of how he designed the device and what kinds of issues he ran into while doing so. For example, he says Fusion 360 doesn’t simulate ball and socket joints well, so he had to resort to printing a bunch of prototypes to iterate until he found the right ones. Also, the cradle that holds the Xbox controller was far more difficult to design than expected, because while Valve might provide accurate CAD models of their controllers, there was no such resource for the Xbox ones. You can watch the whole video, embedded below.
Alumni from Innovation Design Engineering at Imperial College London and the Royal College of Art want to raise awareness of a road pollution source we rarely consider: tire wear. If you think about it, it is obvious. Our tires wear out, and that has to go somewhere, but what surprises us is how fast it happens. Single-use plastic is the most significant source of oceanic pollution, but tire microplastics are next on the naughty list. The team calls themselves The Tyre Collective, and they’re working on a device to collect tire particles at the source.
News comes overnight that the Windows XP source code has been leaked. The Verge says they have “verified the material as legitimate” and that the leak also includes Windows Server 2003 and some DOS and CE code as well. The thing is, it has now been more than six years since Microsoft dropped support for XP, does it really matter if the source code is made public?
The Poison Pill
As Erin Pinheiro pointed out in her excellent article on the Nintendo IP leak earlier this year (perhaps the best Joe Kim artwork of the year on that one, by the way), legitimate developers can’t really make use of leaked code since it opens them up to potential litigation. Microsoft has a formidable legal machine that would surely go after misuse of the code from a leak like this. Erin mentions in her article that just looking at the code is the danger zone for competitors.
Even if other software companies did look at the source code and implement their own improvements without crossing the legal line, how much is there still to gain? Surely companies with this kind of motivation would have reverse engineered the secret sauce of the long dead OS by now, right?
Spy vs. Spy
The next thing that comes to mind are the security implications. At the time of writing, statcount pegs Windows XP at a 0.82% market share which is still going to be a very large number of machines. Perhaps a better question to consider is what types of machines are still running it? I didn’t find any hard data to answer this question, however there are dedicated machines like MRIs that don’t have easy upgrade paths and still use the OS and there is an embedded version of XP that runs on point-of-sale, automated teller machines, set-top boxes, and other long-life hardware that are notorious for not being upgraded by their owners.