The average person’s experience with an ultraviolet (UV) wand is getting a cavity at the dentist. However, anyone with a resin-based 3d printer knows how important a UV curing system is. Often times some spots on a print need a little bit of extra UV to firm up. [Mile] has set out to create an open-source UV curing wand named Photon that is cost-effective and easy to build.

What’s interesting here is that there are dozens if not hundreds of UV curing systems ranging from $5 LED flashlights to larger industrial flood systems. [Mile] dives right in and shows the trade-offs that those cheaper modules are making as well as what the commercial systems are doing that he isn’t. [Mile’s] Photon wand tries to be energy efficient with more irradiated power while staying at a lower cost. This is done by carefully selecting the CSP LEDs instead of traditional wire-bonded and making sure the light source is properly focused and cooled. From the clean PCB and slick case, it is quite clear that [Mile] has gone the extra step to make this production-friendly. Since there are two industry-standard wavelengths that resins cure at (364nm and 405nm), the LED modules in Photon are user-replaceable.

What we love about this project is looking past what is readily available and diving deep. First understanding the drawbacks and limitations of what is there, then setting a goal and pushing through to something different. This isn’t the first UV curing tool we’ve seen recently, so it seems there is a clear need for something better that’s what is out there today.

The HackadayPrize2020 is Sponsored by:

source https://hackaday.com/2020/12/06/a-uv-curing-wand-for-everyone/

The average person’s experience with an ultraviolet (UV) wand is getting a cavity at the dentist. However, anyone with a resin-based 3d printer knows how important a UV curing system is. Often times some spots on a print need a little bit of extra UV to firm up. [Mile] has set out to create an open-source UV curing wand named Photon that is cost-effective and easy to build.

What’s interesting here is that there are dozens if not hundreds of UV curing systems ranging from $5 LED flashlights to larger industrial flood systems. [Mile] dives right in and shows the trade-offs that those cheaper modules are making as well as what the commercial systems are doing that he isn’t. [Mile’s] Photon wand tries to be energy efficient with more irradiated power while staying at a lower cost. This is done by carefully selecting the CSP LEDs instead of traditional wire-bonded and making sure the light source is properly focused and cooled. From the clean PCB and slick case, it is quite clear that [Mile] has gone the extra step to make this production-friendly. Since there are two industry-standard wavelengths that resins cure at (364nm and 405nm), the LED modules in Photon are user-replaceable.

What we love about this project is looking past what is readily available and diving deep. First understanding the drawbacks and limitations of what is there, then setting a goal and pushing through to something different. This isn’t the first UV curing tool we’ve seen recently, so it seems there is a clear need for something better that’s what is out there today.

The HackadayPrize2020 is Sponsored by:

source https://hackaday.com/2020/12/06/a-uv-curing-wand-for-everyone/

By now you’ve no doubt heard of the sudden but not unexpected demise of the iconic Arecibo radio telescope in Puerto Rico. We have been covering the agonizing end of Arecibo from almost the moment the first cable broke in August to a eulogy, and most recently its final catastrophic collapse this week. That last article contained amazing video of the final collapse, including up-close and personal drone shots of the cable breaking. For a more in-depth analysis of the collapse, it’s hard to beat Scott Manley’s frame-by-frame analysis, which really goes into detail about what happened. Seeing the paint spalling off the cables as they stretch and distort under loads far greater than they were designed for is both terrifying and fascinating.

Exciting news from Australia as the sample return capsule from JAXA’s Hayabusa2 asteroid explorer returned safely to Earth Saturday. We covered Hayabusa2 in our roundup of extraterrestrial excavations a while back, describing how it used both a tantalum bullet and a shaped-charge penetrator to blast regolith from the surface of asteroid 162173 Ryugu. Samples of the debris were hoovered up and hermetically sealed for the long ride back to Earth, which culminated in the fiery re-entry and safe landing in the midst of the Australian outback. Planetary scientists are no doubt eager to get a look inside the capsule and analyze the precious milligrams of space dust. In the meantime, Hayabusa2, with 66 kilograms of propellant remaining, is off on an extended mission to visit more asteroids for the next eleven years or so.

The 2020 Remoticon has been wrapped up for most of a month now, but one thing we noticed was how much everyone seemed to like the Friday evening Bring-a-Hack event that was hosted on Remo. To kind of keep that meetup momentum going and to help everyone slide into the holiday season with a little more cheer, we’re putting together a “Holiday with Hackaday & Tindie” meetup on Tuesday, December 15 at noon Pacific time. The details haven’t been shared yet, but our guess is that this will certainly be a “bring-a-hack friendly” event. We’ll share more details when we get them this week, but for now, hop over to the Remo event page and reserve your spot.

On the Buzzword Bingo scorecard, “Artificial Intelligence” is a square that can almost be checked off by default these days, as companies rush to stretch the definition of the term to fit almost every product in the neverending search for market share. But even those products that actually have machine learning built into them are only as good as the data sets used to train them. That can be a problem for voice-recognition systems; while there are massive databases of utterances in just about every language, the likes of Amazon and Google aren’t too willing to share what they’ve leveraged from their smart speaker using customer base. What’s the little person to do? Perhaps the People’s Speech database will help. Part of the MLCommons project, it has 86,000 hours of speech data, mostly derived from audiobooks, a clever source indeed since the speech and the text can be easily aligned. The database also pulls audio and the corresponding text from Wikipedia and other random sources around the web. It’s a small dataset, to be sure, but it’s a start.

And finally, divers in the Baltic Sea have dredged up a bit of treasure: a Nazi Engima machine. Divers in Gelting Bay near the border of Germany and Denmark found what appeared to be an old typewriter caught in one of the abandoned fishing nets they were searching for. When they realized what it was — even crusted in 80-years-worth of corrosion and muck some keys still look like they’re brand new — they called in archaeologists to take over recovery. Gelting Bay was the scene of a mass scuttling of U-boats in the final days of World War II, so this Engima may have been pitched overboard before by a Nazi commander before pulling the plug on his boat. It’ll take years to restore, but it’ll be quite a museum piece when it’s done.

source https://hackaday.com/2020/12/06/hackaday-links-december-6-2020/

Human ears are capable of perceiving frequencies from roughly 20 Hz up to 20 kHz, at least when new. Correspondingly, our audio hardware is designed more or less to target these frequencies. However, there’s often a little extra capability at the upper edges, which [Jacek] shows can be exploited to exfiltrate data.

The hack takes advantage of the fact that most computers can run their soundcards at a sample rate of up to 48 kHz, which thanks to the Nyquist theorem means they can output frequencies up to around 24 kHz — still outside the range of human hearing. Computers and laptops often use small speaker drivers too, which are able to readily generate sound at this frequency. Through the use of a simple Linux shell script, [Jacek] is able to have a laptop output Morse code over ultrasound, and pick it up with nothing more than a laptop’s internal microphone at up to 20 meters away.

[Jacek] enjoys exploring alternative data exfiltration methods; he’s previously experimented with Ethernet leaks on the Raspberry Pi. Of course, with any airgap attack, the real challenge is often getting the remote machine to run the exfiltration script when there’s no existing remote admin access to be had. Video after the break.

source https://hackaday.com/2020/12/06/leaking-data-by-ultrasound/

Finding out you’ve got a flat tyres halfway into a long ride is a frustrating experience for a cyclist. Maintaining the

correct tyre pressures is key to a good ride, whether you’re stacking up the miles on the road or tackling tricky single track in the mountains. [CaptMcAllister] has put together a device that makes keeping an eye on your tyres easy.

The device consists of an ultra low power microcontroller from Texas Instruments, paired with a pressure sensor. Set up for Near Field Communication, or NFC, it’s designed to be powered by the smartphone that queries the microcontroller for a reading. We featured a prototype back in 2015 which required mounting the device within the inner tube of the tyre itself. However, this required invasive installation and the devices tended to wear out over time due to flex damaging the delicate copper coil antenna.

The new design consists of the same microcontroller hardware, but mounted in a modified valve extension that fits to the fill valve of the bicycle tyre. The PCB is directly epoxied on to the valve extension, ensuring air can’t leak out over time. The assembly is then overmoulded in an injection moulding process to provide further sealing and protection against the elements. This should help immensely in rough-and-tumble mountain biking applications.

The new device provides a simple screw-on solution for tire pressure monitoring that’s set and forget — no batteries required. [CaptMcAllister] is currently investigating options for a production run, and given the simple design, we imagine it couldn’t be too hard to rattle off a few hundred or thousand units. We could imagine it would also pair well with a microcontroller, NFC reader, and a display setup on the handlebars to give live readings where required. We look forward in earnest to seeing where this project goes next!

source https://hackaday.com/2020/12/06/no-battery-pressure-sensors-for-bike-tyres/

When we first saw [Barqunics’] design for a self-stabilizing spoon for people suffering from Parkinson’s disease, we wondered how well something like that could work. But take a look at the video below and you’ll see this does a fine job of responding to the user’s hand movements and keeping the spoon perfectly level through a wide range of motion.

There’s at least one commercial product that attempts to stabilize a spoon in the same way so that people suffering from that affliction can retain a measure of independence. This shows that you don’t need injection molding and factory made boards to prove the concept. An MPU6050 provides sensor information and two servo motors control the spoon using PID control.

PID — short for proportional, integral, derivative — is a way to adjust something to a desired point. For example, consider trying to heat a cup of water to 95 °C. If you simply turn the heater on full blast until you get to 95 °C, the water will actually get hotter because you’ll overshoot. Using PID, the amount of heating provided will depend on how far off you are now (proportional), how far off you’ve been over the long term (integral), and how much change you’ve effected recently (derivative). The same algorithm works for spoon-balancing and many other types of controls.

This isn’t the first bootstrapped assistive spoon project we’ve seen. We even looked at the commercial version, awhile back.

source https://hackaday.com/2020/12/06/parkinsons-spoon-uses-control-theory-for-good/

Sometimes when a piece of electronics lands on the bench, you find that its chips have their markings sanded off. The manufacturer is trying to make the task of the reverse engineer less easy, thus protecting their market. [Maurizio Butti] found an unexpected one in an electronic switch designed for remote control systems, it had the simple job of listening to the PWM signal from a receiver in a model aircraft or similar and opening or closing a FET.

From previous experience he suspected it might be a microcontroller from STC based on the location of power, ground, Rx, and Tx pins. This 8051-compatible device could be readily reprogrammed, so he has able to create his own firmware for it. He’s published the code and it’s pretty simple, as it simply replicates the original. He acknowledges that this might seem odd, but makes the point that it is left open for future upgrades such as for example repeatedly cycling the output as in a flashing light.

We don’t see so much of the STC chips here aside from one of their earlier offerings, but the 8051 core features here more regularly as it’s found in Nordic’s NRF24 series of wireless-capable chips.

source https://hackaday.com/2020/12/06/ground-off-part-number-leads-to-chip-detective-work/

Chain link fences are woven with a mechanism that is almost hypnotic to watch, so [Levsha] decided to build his own tiny hand-crank tabletop version to make tiny copper wire fences.

Chain link consist of a series of wires bent and woven in a zigzag pattern. The zigzag bends are made by winding the wire around a rotating flat plate inside a stationary tube with a spiral slot in the side to keep the spacing of the bends consistent. [Levsha]’s version is roughly 1/10 scale of the real thing, and only does the bending and winding parts. Linking the bent wire together is up to the operator. All the components were machined on a lathe and CNC router, and beautifully finished and assembled on a wood base. The hardest part was the tube with the spiral slot, which took a few attempts to get right. [Levsha] initially tried to use steel wire, but it was too stiff and caused the winding mechanism to lock up. 0.4 mm copper wire turned out to be the best choice.

Although there is no practical use for this device that we can see, the craftsmanship is excellent, and it is one of those videos that reminds us how badly we want some machine tools.

Fine attention to detail is really what makes videos like this enjoyable to watch. Wee seen a few other such project, like a beautiful scratch-built lathe, or a pneumatic powered drone that can’t fly.

source https://hackaday.com/2020/12/06/tiny-chain-link-fence-made-with-hand-cranked-brilliance/

Controlling blinds using off the shelf solutions can be expensive – more so if you have multiple blinds you want to control. [HumanSkunk87] felt the cost was too high, so they designed a controller to automatically open and close the blinds.

The main part of this build is a motor and a ball chain gear – a wheel that captures the balls of a ball chain so that the chain can be pulled. The wheel was designed using Fusion3D and then printed out. The motor requires enough power to pull the chain — [HumanSkunk87] figures it needs to be able to pull about 2.5kg in order to raise the blind. After giving up on stepper motors, a DC motor with a worm gear was found to have enough torque to work. A WEMOS D1 Mini controls the motor controller that drives the ball chain wheel. Two micro switches tell the WEMOS when to stop at the bottom and top of the window.

The WEMOS is programmed using ESPHome and it connects to [HumanSkunk87]’s HomeAssistant to complete the automation. Check out the descriptions in the link for the parts and the code used to run everything. There are many other creative ways to open your blinds, It’s even possible to automate curtains instead of blinds.

View post on imgur.com

[via reddit]

source https://hackaday.com/2020/12/05/diy-automated-roller-blinds/

For some reason, when slot machines went digital, they lost their best feature — the handle. Who wants to push a button on a slot machine, anyway? Might as well just play video poker. [John Bradnam] seems to agree, and has built an open-source three-color matrix slot machine complete with handle.

In this case, you’ll be losing all of your nickels to an Arduino Pro Mini. The handle is an upgrade to an earlier slot machine project that uses three 8×8 matrices and a custom driver board. When the spring-loaded handle is pulled, it strikes a micro switch to spins the reels and then snaps back into place. Between each pull, the current score is displayed across the matrix. There’s even a piezo buzzer for victory squawks. We only wish the button under the handle were of the clickier variety, just for the feels. Check out the short demo video after the break.

If you’re not a gambler, you could always turn your slot machine into a clock.

source https://hackaday.com/2020/12/05/slot-machine-has-a-handle-on-fun/

With the coronavirus raging worldwide, 2020 has seen major shortages of personal protective equipment impact healthcare workers and individuals alike. This has led many to improvise their own solutions. One of the more complete offerings we’ve seen is this hybrid respirator build from [Ben Howard].

[Ben’s] build goes above and beyond the usual craft project masks. It uses a laser-cut chipboard frame to fit three HEPA filters, originally designed for the Roomba robotic vacuum cleaner. Two are used for exhalation, while one is used for inhalation. A small blower fan is installed with the intake filter, to provide mild positive pressure when breathing in. The assembly is wrapped up in fabric, using layers of spandex, fleece, and ripstop nylon to provide the best possible seal against the wearer’s face.

It’s a build that should appeal to those who want to breathe cleaner air and also protect others from exhaled particles that can spread respiratory viruses. We’ve seen all kind of masks hit the scene this year; the graphene-impregnated variety is one of the more interesting designs. Still, one can hope that future years lead to less reliance on such measures!

source https://hackaday.com/2020/12/05/hybrid-respirator-uses-repurposed-filters/

In 2020 when we carry an all-purpose computer and data terminal able to store our every thought and deed on a global computer network, it’s easy to forget that once upon a time we were excited by the simpler things. Take the camcorder for example, back in the 1990s the idea of a complete video recording solution that captured moving images on tape cartridges and fit in the palm of your hand was a very big deal indeed, and camcorders as we called them in those innocent times were a prized posession. Now they’re a $0.50 find a Goodwill, which is how [Dustin] picked up the RCA camcoder he’s converting into something altogether more modern. He’s gutted it and upgraded it by removing the analogue innards and retaining only the case and lens assembly to put around a Raspberry Pi and associated HQ camera module.

Opening the camcorder up reveals a ton of miniaturised analogue circuitry, but once the original assemblies are removed it’s relatively straightforward to put the Pi camera on the rear of the lens unit. There’s plenty of space for the Pi in the box, and he’s putting a touchscreen on the outside.

Sadly the camcorder’s original tiny CRT is no longer working, else that would have been the ultimate retro viewfinder. Still we hope to see some tinkering on that part of the project since those little CRTS make for delightful hacks. The project is very much a work in progress, but should serve that these once ubiquitous devices are now in the realm of the throwaway.

This isn’t the first such conversion we’ve seen with a Raspberry Pi, the original camera module is a handy fit to an 8mm movie camera.

source https://hackaday.com/2020/12/05/a-retro-camcorder-upgraded-as-a-raspberry-pi-hq-camera/

Imagine that you’re serving on a jury, and you’re given an image taken from a surveillance camera. It looks pretty much like the suspect, but the image has been “enhanced” by an AI from the original. Do you convict? How does this weigh out on the scales of reasonable doubt? Should you demand to see the original?

AI-enhanced, upscaled, or otherwise modified images are tremendously realistic. But what they’re showing you isn’t reality. When we wrote about this last week, [Denis Shiryaev], one of the authors of one of the methods we highlighted, weighed in the comments to point out that these modifications aren’t “restorations” of the original. While they might add incredibly fine detail, for instance, they don’t recreate or restore reality. The neural net creates its own reality, out of millions and millions of faces that it’s learned.

And for the purposes of identification, that’s exactly the problem: the facial features of millions of other people have been used to increase the resolution. Can you identify the person in the pixelized image? Can you identify that same person in the resulting up-sampling? If the question put before the jury was “is the defendant a former president of the USA?” you’d answer the question differently depending on which image you were presented. And you’d have a misleading level of confidence in your ability to judge the AI-retouched photo. Clearly, informed skepticism on the part of the jury is required.

Unfortunately, we’ve all seen countless examples of “zoom, enhance” in movies and TV shows being successfully used to nab the perps and nail their convictions. We haven’t seen nearly as much detailed analysis of how adversarial neural networks create faces out of a scant handful of pixels. This, combined with the almost magical resolution of the end product, would certainly sway a jury of normal folks. On the other hand, the popularity of intentionally misleading “deep fakes” might help educate the public to the dangers of believing what they see when AI is involved.

This is just one example, but keeping the public interested in and educated on the deep workings and limitations of the technology that’s running our world is more important than ever before, but some of the material is truly hard. How do we separate the science from the magic?

source https://hackaday.com/2020/12/05/sufficiently-advanced-technology-and-justice/

Over the last couple of years the cyberdeck community has absolutely exploded. Among those who design and build these truly personal computers there are no hard rules, save perhaps making sure the final result looks as unconventional as possible. But one thing that’s remained fairly consistent is the fact that these machines are almost exclusively powered by the Raspberry Pi. Unfortunately, that means they often leave something to be desired in terms of raw performance.

But [MSG] had a different idea. His cyberdeck still has the customary Raspberry Pi inside, but it also has an i7 Intel NUC that can be fired up at the touch of a button. He says it’s the best of both worlds: an energy efficient ARM Linux platform for mobile experimentation, and a powerful x86 Windows box for playing games working from home. It’s the hacker equivalent of business in the front, party in the back.

With a KVM connected to the custom Planck 40% mechanical keyboard and seven inch LCD, [MSG] can switch between both systems on the fly. Assuming he’s got the juice anyway; while the Raspberry Pi 4 and LCD is able to run on a pair of 18650 batteries, the cyberdeck needs to be plugged in if he wants to use the power-hungry NUC. If he ditched the Pi he could potentially load up the case with enough batteries to get the Intel box spun up, but that would be getting a little too close to a conventional laptop.

The whole plurality theme doesn’t stop at the computing devices, either. In addition to the primary LCD, there’s also a 2.13 inch e-paper display and a retro-style LED matrix courtesy of a Pimoroni Micro Dot pHAT. With a little Python magic behind the scenes, [MSG] is able to display things like the system temperature, time, and battery percentage even when the LCD is powered down.

In a post on the aptly-named Cyberdeck Cafe, [MSG] talks about how seeing the VirtuScope built by [bootdsc] inspired him to start working towards his own personal deck, and where he hopes to take the idea from here. The unique USB expansion bay behind the screen holds particular promise, and it sounds like a few add-on modules are already in the works. But of course, it wouldn’t be a true cyberdeck if it wasn’t constantly being improved and redesigned. Come to think of it, that makes at least two rules to live by in this community.

source https://hackaday.com/2020/12/05/arm-and-x86-team-up-in-no-compromise-cyberdeck/

Building radio receivers from scratch is still a popular project since it can be done largely with off-the-shelf discrete components and a wire long enough for the bands that the radio will receive. That’s good enough for AM radio, anyway, but you’ll need to try this DIY FM receiver if you want to listen to something more culturally relevant.

Receiving frequency-modulated radio waves is typically more difficult than their amplitude-modulated cousins because the circuitry necessary to demodulate an FM signal needs a frequency-to-voltage conversion that isn’t necessary with AM. For this build, [hesam.moshiri] uses a TEA5767 FM chip because of its ability to communicate over I2C. He also integrated a 3W amplifier into this build, and everything is controlled by an Arduino including a small LCD screen which displays the current tuned frequency. With the addition of a small 5V power supply, it’s a tidy and compact build as well.

While the FM receiver in this project wasn’t built from scratch like some AM receivers we’ve seen, it’s still an interesting build because of the small size, I2C capability, and also because all of the circuit schematics are available for all of the components in the build. For those reasons, it could be a great gateway project into more complex FM builds.

source https://hackaday.com/2020/12/04/fm-radio-from-scratch-using-an-arduino/

While it does use the same M12 batteries, this impeccably engineered work light isn’t an official Milwaukee product. It’s the latest creation from [Chris Chimienti], who’s spent enough time in the garage and under the hood to know a thing or two about what makes a good work light. The modular design not only allows you to add or subtract LED panels as needed, but each section is able to rotate independently so it points exactly where you need it.

Magnets embedded in the 3D printed parts mean the light modules not only firmly attach to one another, but can be stuck to whatever you’re working on. Or you could just stack all the lights up vertically and use the rocket-inspired “landing legs” of the base module keep it vertical. Even if the light gets knocked around, the tension provided by rubber bands attached to each fold-out leg means it will resist falling over. In the video after the break [Chris] says the little nosecone on top is just for fun and you don’t have to print it, but we don’t see how you can possibly resist.

Of course, 3D printed parts and magnets don’t self-illuminate. The LED panels and switches are salvaged from cheap lights that [Chris] found locally for a few bucks, and a common voltage regulator board is used to step the 12 volts coming from the Milwaukee battery down to something the LEDs can use. He’s designed a very slick reversible PCB that’s used on either end of each light module to transfer power between them courtesy of semi-circular traces on one side and and matching pogo pins on the other.

As we saw in his recent Dremel 3D20 rebuild, [Chris] isn’t afraid to go all in during the design phase. The amount of CAD work that went into this project is astounding, and serves as fantastic example of the benefits to be had by designing the whole assembly at once rather than doing it piecemeal. It might take longer early on, but the final results really speak for themselves.

source https://hackaday.com/2020/12/04/transforming-work-light-is-more-than-meets-the-eye/

What do you get when you stick 1738 MOSFETs together? If your answer was a ‘4-bit CPU’, you would be totally correct. Available as a product over at Marutsu as the ‘CPU1738’, it seems to target beginners to computer theory, with build instructions that explain how the CPU is built up from individual MOSFETs that are combined into logic gates.

While decidedly more compact in its SMD format than it would have been with pure through-hole parts, the use of countless small PCBs on top of the larger PCBs make for a pretty hefty package. Board after board build up the CPU, and the assembly continues with the addition of sensors, motors, and wheels. In the end, a robot emerges, albeit a somewhat wobbly-looking one.

Check out the video linked after the break, though before starting one up, note the 50,000 Yen (approximately $500) price tag for the CPU block alone. On the other hand, in addition to the 1738 MOSFETs, there are also 1070 LEDs, so you get what you pay for in blinkies.

source https://hackaday.com/2020/12/04/incredible-discrete-mosfet-rover-has-maximum-blink/

What do you get when you stick 1738 MOSFETs together? If your answer was a ‘4-bit CPU’, you would be totally correct. Available as a product over at Marutsu as the ‘CPU1738’, it seems to target beginners to computer theory, with build instructions that explain how the CPU is built up from individual MOSFETs that are combined into logic gates.

While decidedly more compact in its SMD format than it would have been with pure through-hole parts, the use of countless small PCBs on top of the larger PCBs make for a pretty hefty package. Board after board build up the CPU, and the assembly continues with the addition of sensors, motors, and wheels. In the end, a robot emerges, albeit a somewhat wobbly-looking one.

Check out the video linked after the break, though before starting one up, note the 50,000 Yen (approximately $500) price tag for the CPU block alone. On the other hand, in addition to the 1738 MOSFETs, there are also 1070 LEDs, so you get what you pay for in blinkies.

source https://hackaday.com/2020/12/04/incredible-discrete-mosfet-rover-has-maximum-blink/

What do you get when you stick 1738 MOSFETs together? If your answer was a ‘4-bit CPU’, you would be totally correct. Available as a product over at Marutsu as the ‘CPU1738’, it seems to target beginners to computer theory, with build instructions that explain how the CPU is built up from individual MOSFETs that are combined into logic gates.

While decidedly more compact in its SMD format than it would have been with pure through-hole parts, the use of countless small PCBs on top of the larger PCBs make for a pretty hefty package. Board after board build up the CPU, and the assembly continues with the addition of sensors, motors, and wheels. In the end, a robot emerges, albeit a somewhat wobbly-looking one.

Check out the video linked after the break, though before starting one up, note the 50,000 Yen (approximately $500) price tag for the CPU block alone. On the other hand, in addition to the 1738 MOSFETs, there are also 1070 LEDs, so you get what you pay for in blinkies.

source https://hackaday.com/2020/12/04/incredible-discrete-mosfet-rover-has-maximum-blink/

There are a lot of keyboards to choose from, and a quick trip through some of the forums will quickly show you how fanatical some people can be about very specific styles or switches. [Crdotson] doesn’t seem to be too far down the rabbit hole in that regard, but he does have a keyboard that he really likes despite one small quirk: it’s built for Mac, and some of the modifier keys aren’t laid out correctly for Windows. Since Windows has limited (and poor) options for software keymapping, he took an alternative route and built a keymapper in hardware instead.

The build uses a Raspberry Pi as a go-between from the keyboard to his computer. The Pi watches the USB bus using usbmon, which allows inspection of the packets and can see which keys have been pressed. It then passes those keypresses through to the computer. His only modification to the keyboard mapping is to swap the Alt and Super (Windows) keys for his keyboard of choice, although using this software would allow any other changes to be made as well. Latency is only on the order of a few microseconds, which is not noticeable for normal use cases.

While we have seen plenty of other builds around that can map keyboards in plenty of custom ways, if you don’t have the required hardware for a bespoke solution it’s much more likely that there’s a Raspberry Pi laying around that can do the job instead. There are a few issues with the build that [crdotson] is planning to tackle, though, such as unplugging the device while a key is being pressed, which perpetually sends that keystroke to the computer without stopping. But for now it’s a workable solution for his problem.

source https://hackaday.com/2020/12/03/hardware-keymapper-routes-through-raspberry-pi/

An anonymous reader pinged us about an issue that affects people who jumped onto the latest-and-greatest OS from the Apple gardens: USB devices that stop working due to the FTDI-based USB solution. At its core appears to be that the built-in FTDI driver provided by Apple (AppleUSBFTDI.dext) only supports FTDI chips which provide the standard FTDI vendor and product ID (e.g. 0x0403 and 0x6001 respectively for the FT232R). Many products however set a custom product ID (PID) to differentiate their device, though in the thread some mention that there are driver issues even with the default VID/PID combination.

Over the past years, Apple has been restricting and changing the way kernel extensions (KExt) and driver extensions (DExt) are handled. As these FTDI chips are often used for virtual com port (VCP) purposes, such as with Arduino boards and USB-TTL adapters, this is a rather cumbersome issue that would affect anyone using Big Sur in combination with such a hardware device.

So far only the FTDI team has been somewhat responsive based on the support forum thread, with Apple seemingly rather silent on the issue.

source https://hackaday.com/2020/12/03/ftdi-vcp-chips-with-custom-pids-not-working-on-macos-11-big-sur/

Today the National Science Foundation released a pair of videos that document the collapse of the Arecibo Observatory with incredible detail. A wide shot, apparently taken from the Visitors Center, shows the 900 ton instrument platform breaking free and swinging on the remaining support cables until it smashes into the edge of the dish. The second clip, recorded by an airborne drone, is focused directly on the cables as they failed. Both can be seen in the video embedded below.

Together, they produce an invaluable visual record of what finally brought the iconic radio telescope down. As was predicted by engineers earlier in the month, the failure of another support cable on tower 4 triggered a chain reaction that brought the entire platform crashing down onto the 305 meter reflector. Footage from a drone observing the top of tower 4 shows that the entire sequence, from the first visual wire break to the remaining cables being torn from their mounts, only took five seconds. While some initially doubted the NSF’s determination that it was too dangerous to repair Arecibo, this footage seems to prove just how tenuous the structural integrity of the Observatory really was.

These videos will hopefully help investigators who still need to determine why the cables failed in the first place. The cable in August didn’t snap, it simply pulled lose from its mount. It was suspected that the cable may have been incorrectly installed, but as it was only a backup, the situation was not seen as critical. But when the second cable failed in November it was found to have snapped at just 60% of its minimum breaking strength.

This immediately called into question the condition of the remaining cables, and ultimately lead to the decision by the NSF to proceed with a controlled demolition of the Observatory that would preserve as much of the scientific equipment as possible. Unfortunately, the remaining cables didn’t last long enough to put that plan into action.

After the cleanup, investigators will have the opportunity to examine the cables in an effort to find out what caused their premature failure. Was there some design or manufacturing flaw that meant they were always dangerously overrated? Or perhaps investigators will confirm what many already fear; that humanity has lost a one of a kind scientific instrument due to dwindling financial support and lax maintenance procedures.

source https://hackaday.com/2020/12/03/nsf-releases-video-of-arecibos-final-moments/

Today the National Science Foundation released a pair of videos that document the collapse of the Arecibo Observatory with incredible detail. A wide shot, apparently taken from the Visitors Center, shows the 900 ton instrument platform breaking free and swinging on the remaining support cables until it smashes into the edge of the dish. The second clip, recorded by an airborne drone, is focused directly on the cables as they failed. Both can be seen in the video embedded below.

Together, they produce an invaluable visual record of what finally brought the iconic radio telescope down. As was predicted by engineers earlier in the month, the failure of another support cable on tower 4 triggered a chain reaction that brought the entire platform crashing down onto the 305 meter reflector. Footage from a drone observing the top of tower 4 shows that the entire sequence, from the first visual wire break to the remaining cables being torn from their mounts, only took five seconds. While some initially doubted the NSF’s determination that it was too dangerous to repair Arecibo, this footage seems to prove just how tenuous the structural integrity of the Observatory really was.

These videos will hopefully help investigators who still need to determine why the cables failed in the first place. The cable in August didn’t snap, it simply pulled lose from its mount. It was suspected that the cable may have been incorrectly installed, but as it was only a backup, the situation was not seen as critical. But when the second cable failed in November it was found to have snapped at just 60% of its minimum breaking strength.

This immediately called into question the condition of the remaining cables, and ultimately lead to the decision by the NSF to proceed with a controlled demolition of the Observatory that would preserve as much of the scientific equipment as possible. Unfortunately, the remaining cables didn’t last long enough to put that plan into action.

After the cleanup, investigators will have the opportunity to examine the cables in an effort to find out what caused their premature failure. Was there some design or manufacturing flaw that meant they were always dangerously overrated? Or perhaps investigators will confirm what many already fear; that humanity has lost a one of a kind scientific instrument due to dwindling financial support and lax maintenance procedures.

source https://hackaday.com/2020/12/03/nsf-releases-video-of-arecibos-final-moments/

Today the National Science Foundation released a pair of videos that document the collapse of the Arecibo Observatory with incredible detail. A wide shot, apparently taken from the Visitors Center, shows the 900 ton instrument platform breaking free and swinging on the remaining support cables until it smashes into the edge of the dish. The second clip, recorded by an airborne drone, is focused directly on the cables as they failed. Both can be seen in the video embedded below.

Together, they produce an invaluable visual record of what finally brought the iconic radio telescope down. As was predicted by engineers earlier in the month, the failure of another support cable on tower 4 triggered a chain reaction that brought the entire platform crashing down onto the 305 meter reflector. Footage from a drone observing the top of tower 4 shows that the entire sequence, from the first visual wire break to the remaining cables being torn from their mounts, only took five seconds. While some initially doubted the NSF’s determination that it was too dangerous to repair Arecibo, this footage seems to prove just how tenuous the structural integrity of the Observatory really was.

These videos will hopefully help investigators who still need to determine why the cables failed in the first place. The cable in August didn’t snap, it simply pulled lose from its mount. It was suspected that the cable may have been incorrectly installed, but as it was only a backup, the situation was not seen as critical. But when the second cable failed in November it was found to have snapped at just 60% of its minimum breaking strength.

This immediately called into question the condition of the remaining cables, and ultimately lead to the decision by the NSF to proceed with a controlled demolition of the Observatory that would preserve as much of the scientific equipment as possible. Unfortunately, the remaining cables didn’t last long enough to put that plan into action.

After the cleanup, investigators will have the opportunity to examine the cables in an effort to find out what caused their premature failure. Was there some design or manufacturing flaw that meant they were always dangerously overrated? Or perhaps investigators will confirm what many already fear; that humanity has lost a one of a kind scientific instrument due to dwindling financial support and lax maintenance procedures.

source https://hackaday.com/2020/12/03/nsf-releases-video-of-arecibos-final-moments/

Underwater Remote Operated Vehicles, or ROVs as they’re typically known, generally operate by tether. This is due to the poor propagation of radio waves underwater. [Simon] wanted to build such a drone, but elected to go for an alternative design with less strings attached, so to speak. Thus far, there have been challenges along the way.

The underwater drone uses a 3D printed chassis, replete with googly eyes that go a long way to anthropomorphizing the build. Four motors are used for control, with two for thrust in the horizontal plane and two mounted in the vertical plane for attitude control. This allows the drone to be set up at neutral buoyancy, and moved through the water column with thrust rather than complicated ballast mechanisms. The build aims to eschew tethers, instead using a shorter cable to link to a floating unit which uses radio to communicate with the operator on the shore.

The major struggle facing the build has been sealing the chassis against water ingress. This is where the layered nature of 3D printing is a drawback. Even with several treatments of paint and sealant, [Simon] has been unable to stop water getting inside the drone. Further problems concern the excess amount of ballast required to counteract the drone’s natural buoyancy due to displacement.

Regardless of the struggles, we look forward to seeing the next revision rectify some of the shortcomings of the current build. We’re sure [Simon’s] experience building an electric surfboard will come in handy. Video after the break.

source https://hackaday.com/2020/12/03/underwater-drone-faces-trial-by-water/