Do you need more proof that we’re living in the future? A group of MIT engineers have found a way for spinach, aka Popeye’s favorite short-term strength booster, to send potentially lifesaving emails regarding explosives in the area.

As the team outlined in a paper published in 2016, the field of plant nanobionics uses nanotechnology to enhance the natural abilities of plants and make them do new tricks. Here’s how this one works: the roots of the spinach plants absorb nitroaromatic compounds such as picric acid from the groundwater, and these transpire up through the stem and into the leaves along with water and other nutrients. When the compounds reach the leaves, they accumulate in the plants’ mesophyll — the inner tissue of the leaves.

A pair of sensors made of single-walled carbon nanotubes are built into the leaves. One sensor is engineered to detect nitroaromatic compounds using near-infrared fluorescent emission, and the other is used as a reference signal. As the the compounds build up in the mesophyll, the IR signal gets stronger. This change is detected by a camera, which triggers an email alert to the researchers within a matter of minutes. After running the experiments with a fancy-pants indium-gallium-arsenide camera, the researchers were able to duplicate the results using a Raspberry Pi and a CCD camera module with the infrared filter removed.

Plants have an ear to the groundwater like none other and absorb a lot of information about the environment around them, so the researchers believe that detecting explosive materials is only the beginning — they could also be harbingers of pollution and other environmental concerns.

Even if there is no threat of landmines in the vicinity, weeds are a problem everywhere. There’s a Raspberry Pi-based solution for those, too.

source https://hackaday.com/2021/02/07/sensing-danger-with-spinach/

Sure there are pre-made kits to add a rechargeable battery and USB-C compatibility to Nintendo’s venerable Game Boy Advance, but [HorstBaerbel] thought he could throw together something similar for a fraction of the price. Plus, he wouldn’t have to wait on shipping. The end result might not be quite as polished, but it’s certainly impressive for what’s essentially a junk bin build.

The star of the show is a USB-C variant of the popular TP4056 lithium-ion charger module, which fits nicely inside the original battery compartment while still leaving room for a 1,000 mAh pouch cell. The 4.2 V output of the fully charged battery is a bit too high for the Game Boy’s liking, so [HorstBaerbel] used the forward voltage drop of a diode to bring it down to a more acceptable 3.5 V.

Naturally this does waste a good deal of energy, especially compared to the DC-DC converters used in commercial offerings like the CleanJuice, but it still delivers a respectable seven hours of runtime. The only issue with this modification seems to be that you’ve got just five minutes to save your progress and shut down when the GBA’s low-battery light goes on; but what’s life without a little excitement?

While not nearly extreme as some of the other GBA modifications we’ve seen over the years, this project is yet another example of the seemingly unlimited hacking potential of Nintendo’s iconic Game Boy line.

source https://hackaday.com/2021/02/06/gba-gets-homebrew-usb-c-charging-upgrade/

Sure there are pre-made kits to add a rechargeable battery and USB-C compatibility to Nintendo’s venerable Game Boy Advance, but [HorstBaerbel] thought he could throw together something similar for a fraction of the price. Plus, he wouldn’t have to wait on shipping. The end result might not be quite as polished, but it’s certainly impressive for what’s essentially a junk bin build.

The star of the show is a USB-C variant of the popular TP4056 lithium-ion charger module, which fits nicely inside the original battery compartment while still leaving room for a 1,000 mAh pouch cell. The 4.2 V output of the fully charged battery is a bit too high for the Game Boy’s liking, so [HorstBaerbel] used the forward voltage drop of a diode to bring it down to a more acceptable 3.5 V.

Naturally this does waste a good deal of energy, especially compared to the DC-DC converters used in commercial offerings like the CleanJuice, but it still delivers a respectable seven hours of runtime. The only issue with this modification seems to be that you’ve got just five minutes to save your progress and shut down when the GBA’s low-battery light goes on; but what’s life without a little excitement?

While not nearly extreme as some of the other GBA modifications we’ve seen over the years, this project is yet another example of the seemingly unlimited hacking potential of Nintendo’s iconic Game Boy line.

source https://hackaday.com/2021/02/06/gba-gets-homebrew-usb-c-charging-upgrade/

We’ve been promised hydrogen-powered engines for some time now. One downside though is the need for hydrogen vehicles to have heavy high-pressure tanks. While a 700 bar tank and the accompanying fuel cell is acceptable for a city bus or a truck, it becomes problematic with smaller vehicles, especially ones such as scooters or even full-sized motorcycles. The Fraunhofer Institute wants to run smaller vehicles on magnesium hydride in a paste form that they call POWERPASTE.

The idea is that the paste effectively stores hydrogen at normal temperature and pressure. At 250C, the paste decomposes and releases its hydrogen. While your motorcycle may seem hot when parked in the sun, it isn’t getting quite to 250C.

Interestingly, the paste only provides half the available hydrogen. The rest is from water added start a reaction to release the hydrogen. Fraunhofer claims the energy density available is greater than that of a 700 bar tank in a conventional hydrogen system and ten times more than current battery technology.

One thing that’s attractive is that the paste is easy to store and pump. A gas station, for example, could invest $20-30,000 and dispense the paste from a metal drum to meet low demand and then scale up as needed. A hydrogen pumping setup starts at about $1.2 million. Fraunhofer is building a pilot production plant that will produce about four tons of the material a year.

This isn’t a totally new idea, of course. Using metal hydrides to store hydrogen chemically has other proponents, including French company McPhy energy. There have also been schemes to use other hydrides in powder form as well as chemical hydrogen carriers like formic acid and ammonia.

Will your next drone power itself on paste and water? Probably not for a while although it has been done. If you want to dig into the hydrogen energy economy, [Lewin Day] can fill you in.

source https://hackaday.com/2021/02/06/the-future-of-hydrogen-power-is-paste/

[Ruvin Kub] likes magnets, a lot. Most of his projects feature some sort of magnet and his PC board agitation bath is no exception. You can see a video about the device, below. We’ll admit our Russian is pretty rusty, but if you ask YouTube nicely it will translate the Russian subtitles into whatever language you like.

One of the things we liked about the video was that he uses hydrogen peroxide, citric acid, and salt as an etchant. We’ve seen the same mix with vinegar or muriatic acid instead of citric acid. We aren’t sure what the actual  translation is about why he doesn’t like ferric chloride, but YouTube says, “she’s too gloomy for my light souls.”

There are a few translation glitches, but overall the design is straightforward. A motor moves a little see saw in the base with magnets that repel similar magnets in the tank. In that way, the electronics are isolated from the liquid. The whole affair runs on a rechargeable battery.

As a bonus, in the end, there’s a brief tutorial on making a board with toner transfer along with comparing the time to etch the board with agitation and without. Like a Tootsie Roll Pop, he finally got tired of waiting for the non-agitated board and finished it with agitation. The test board that started in the bath had been done for a long time.

If you want to try different etching solutions, we’ve asked people to share their favorites. Or, just break out that CNC machine.

source https://hackaday.com/2021/02/06/pcb-bath-comes-from-russia-with-love/

For most of us, a lighter is a cheap $2 plastic tool that serves a purpose, and little more. Some of us may go so far as to have a nice Zippo, or perhaps a windproof lighter for better outdoor performance. But if you’re a machinist, you could consider whipping yourself up something special, like this build by [W&M Levsha].

There’s plenty to love here for those who love making chips. The body is crafted out of brass and copper, soldered together by blowtorch. The lighter works by an unusual mechanism. The fluid tank is stuffed with cotton wool and filled with lighter fluid, which feeds a wick, which by itself, is fairly ordinary. However, ignition is via a spring-loaded aluminium hammer, which fires off a paper cap, igniting the wick. The flame can then be extinguished by blowing it out.

It’s a lighter that’s sure to be a conversation piece, though we wonder how welcome it’s cracking report will be at a quiet, reserved cigar bar. The mechanism may have more consumables than a typical lighter, but that’s the price paid to be truly unique. There are other creative designs out there too, like this lighter which uses a platinum catalyst for ignition. Video after the break.

source https://hackaday.com/2021/02/06/cap-gun-lighter-built-from-scratch/

2020 saw many gigabytes of internal Nintendo data leaked on the broader internet. Known as the “Gigaleak”, it contained source codes and assets from many games. Using data from this leak, a group of enthusiasts has put together high-quality renditions of the SNES Super Mario World Original Sound Tracks (OST).

The work was made possible when source code from the Gameboy Advance remake of Super Mario World was found in the leaked data. The source code included the names of the samples, which were the same as were used in the original SNES game. This allowed the team to find the original samples amongst the gigabytes of leaked files.

We wondered what would be done with all that code, speculating that it would be a poison pill for the emulator scene. This type of hack wasn’t even on our radar and we’re delighted to see the project come to light. The reproduced songs have an altogether different quality than the original SNES soundtrack. This is largely due to the samples not having to be compressed or cut down to fit on a cartridge and work with the console’s sound chip. Other variances in the sound also come from the fact that unlike in the game, the samples in these renditions don’t match the play lengths in the original game.

Regardless of the changes, it’s interesting to hear a more full, rounded sound of these classic video game tunes. It reminds us somewhat of the later CD console era, when sound designers were able to break free of the limitations of earlier hardware. Of course, we still bow at the alter of chiptune, though — and this MIDI Gameboy mod is a great place to start if you’re curious. Video after the break.

source https://hackaday.com/2021/02/06/super-mario-original-sound-tracks-get-high-quality-remaster-thanks-to-gigaleak/

We’re knee-deep in new microcontrollers over here, from the new Raspberry Pi Pico to an engineering sample from Espressif that’s right now on our desk. (Spoiler alert, review coming out Monday.) And microcontroller peripherals are a little bit like Pokemon — you’ve just got to catch them all. If a microcontroller doesn’t have 23 UARTS, WiFi, Bluetooth, IR/DA, and a 16-channel 48 MHz ADC, it’s hardly worth considering. More is always better, right?

No, it’s not. Chip design is always a compromise, and who says you’re limited to one microcontroller per project anyway? [Francesco] built a gas-meter reader that reminded to think outside of the single-microcontroller design paradigm. It uses an ATtiny13 for its low power sleep mode, ease of wakeup, and decent ADCs. Pairing this with an ESP8266 that’s turned off except when the ATtiny wants to send data to the network results in a lower power budget than would be achievable with the ESP alone, but still gets his data up into his home-grown cloud.

Of course, there’s more complexity here than a single-micro solution, but the I2C lines between the two chips actually form a natural division of work — each unit can be tested separately. And it’s using each chip for what it’s best at: simple, low-power tasks for the Tiny and wrangling WiFi on the ESP.

Once you’ve moved past the “more is better” mindset, you’ll start to make a mental map of which chips are best for what. The obvious next step is combination designs like this one.

source https://hackaday.com/2021/02/06/the-right-tools-for-the-job/

If it weren’t for persistence of vision, that quirk of biochemically mediated vision, life would be pretty boring. No movies, no TV — nothing but reality, the beauty of nature, and live performances to keep us entertained. Sounds dreadful.

We jest, of course, but POV is behind many cool hacks, one of which is [Joe]’s neat Nipkow disk clock. If you think you’ve never heard of such a thing, you’re probably wrong; Nipkow disks, named after their 19th-century inventor Paul Gottlieb Nipkow, were the central idea behind the earliest attempts at mechanically scanned television. Nipkow disks have a series of evenly spaced, spirally arranged holes that appear to scan across a fixed area when rotated. When placed between a lens and a photosensor, a rudimentary TV camera can be made.

For his Nipkow clock, though, [Joe] turned the idea around and placed a light source behind the rotating disk. Controlling when and what color the LEDs in the array are illuminated relative to the position of the disk determines which pixels are illuminated. [Joe]’s clock uses two LED arrays to double the size of the display area, and a disk with rectangular apertures. The resulting pixels are somewhat keystone-shaped, but it doesn’t really distract from the look of the display. The video below shows the build process and the finished clock in action.

The key to getting the look right in a display like this is the code, and [Joe] put in a considerable effort for his software. If only the early mechanical TV tinkerers had had such help. [Jenny List] did a nice write-up on the early TV pioneers and their Nipkow disk cameras; we’ve also seen other Nipkow displays before, but [Joe]’s clock takes the concept to another level.

source https://hackaday.com/2021/02/06/proto-tv-tech-lies-behind-this-pov-clock/

[Nathan Petersen] built a Hackable Open-Source Thermostat to smooth out temperature fluctuations caused by the large hysteresis of the bimetallic strip thermostat in his apartment. While it may be tempting to adjust the “anticipator” to take care of the problem or even replace the bimetallic thermostat with an electronic version, building your own thermostat from scratch is a good way to add to your project portfolio while making your way through college. Plus, he got to hone his hardware and software design chops.

The hardware is designed around the STM32, using a cheap, minimal variant since the device just needs to sense temperature and control the furnace in on-off mode. The TMP117 high-accuracy, low-power, temperature sensor was selected for temperature measurement since accuracy was an essential feature of the project. Dry-contact output for the furnace is via a normally-open solid state relay (opto-isolator). For the user interface, instead of going the easy-route and using an I²C/SPI OLED or LCD display, [Nathan] used three 7-segment LED displays, each driven by an 8-channel constant current driver. The advantage is that the display can be viewed from across the room, and it’s brightness adjusted via PWM. Temperature set-point adjustment is via a simple slide potentiometer, whose analog voltage is read by the micro-controller ADC. To remind about battery replacement, a second ADC channel on the micro-controller monitors the battery voltage via a voltage divider. The PCB components are mostly surface mount, but the packages selected are easy enough to hand solder.

[Nathan]’s Github repo provides the hardware and firmware source files. The board is designed in Altium, but folks using KiCad can use either the awesome Altium2KiCad converter or the online service for conversion. (The results, with some minor errors that can be easily fixed, are quite usable.) Serendipitously, his PCB layout worked like a charm the first time around, without requiring any rework or bodge wires.

The firmware is a few hundred lines of custom bare-metal C code, consisting of drivers to interface with the hardware peripherals, a UI section to handle the user interface, and the control section with the algorithm for running the furnace. [Nathan] walks us through his code, digging into some control theory and filtering basics. After making a few code tweaks and running the thermostat for some time, [Nathan] concludes that it is able to achieve +0.1°F / -0.5°F temperature regulation with furnace cycles lasting about 10-15 minutes (i.e. 4-6 cycles per hour). Obviously, his well insulated apartment and a decent furnace are also major contributing factors. Moving on, for the next version, [Nathan] wants to add data collection capabilities by adding some memory and SD card storage, and use an RTC to allow seasonal adjustments or time-based set-points.

This is his first attempt at a “functional’ useful project, but he does love to build the occasional toy, such as this POV Top.

source https://hackaday.com/2021/02/06/open-source-thermostat-wont-anger-your-landlord/

The first continuously variable transmission fitted to an automobile actually has its roots in the late 19th century, though the technology has only become popular in the last two decades or so. While a relatively complex technology in its modern automotive form, it’s still possible to illustrate the basic principles with everyone’s favourite mechanical learning toy – Lego.

The build consists of a Lego motor driving the transmission’s input shaft, upon which a cone is mounted. A similar cone is mounted on the output shaft, and a rubber belt stretched between the two. With the cones mounted in opposing directions, the gear ratio can be continually varied by changing where upon the cones the belt rides. By riding on the small diameter section of the input cone, the belt correspondingly rides on the large diameter section of the output cone, leading to a slower, high torque output. By sliding the belt to the other end of the cone, the ratios are reversed, leading to high output speed with less torque.

The demonstration works somewhat differently than modern automotive models, but the basic concept is the same. It’s also limited in its torque transfer ability by the coefficient of friction of the plastic Lego parts. Despite this, it’s a quick way to illustrate the mechanisms at play, and where some of the common losses are in such a system. If you prefer your gearboxes of a more classic sequential design, we’ve seen those too, of course. Video after the break.

source https://hackaday.com/2021/02/05/building-a-continuously-variable-transmission-with-lego/

The first continuously variable transmission fitted to an automobile actually has its roots in the late 19th century, though the technology has only become popular in the last two decades or so. While a relatively complex technology in its modern automotive form, it’s still possible to illustrate the basic principles with everyone’s favourite mechanical learning toy – Lego.

The build consists of a Lego motor driving the transmission’s input shaft, upon which a cone is mounted. A similar cone is mounted on the output shaft, and a rubber belt stretched between the two. With the cones mounted in opposing directions, the gear ratio can be continually varied by changing where upon the cones the belt rides. By riding on the small diameter section of the input cone, the belt correspondingly rides on the large diameter section of the output cone, leading to a slower, high torque output. By sliding the belt to the other end of the cone, the ratios are reversed, leading to high output speed with less torque.

The demonstration works somewhat differently than modern automotive models, but the basic concept is the same. It’s also limited in its torque transfer ability by the coefficient of friction of the plastic Lego parts. Despite this, it’s a quick way to illustrate the mechanisms at play, and where some of the common losses are in such a system. If you prefer your gearboxes of a more classic sequential design, we’ve seen those too, of course. Video after the break.

source https://hackaday.com/2021/02/05/building-a-continuously-variable-transmission-with-lego/

The first continuously variable transmission fitted to an automobile actually has its roots in the late 19th century, though the technology has only become popular in the last two decades or so. While a relatively complex technology in its modern automotive form, it’s still possible to illustrate the basic principles with everyone’s favourite mechanical learning toy – Lego.

The build consists of a Lego motor driving the transmission’s input shaft, upon which a cone is mounted. A similar cone is mounted on the output shaft, and a rubber belt stretched between the two. With the cones mounted in opposing directions, the gear ratio can be continually varied by changing where upon the cones the belt rides. By riding on the small diameter section of the input cone, the belt correspondingly rides on the large diameter section of the output cone, leading to a slower, high torque output. By sliding the belt to the other end of the cone, the ratios are reversed, leading to high output speed with less torque.

The demonstration works somewhat differently than modern automotive models, but the basic concept is the same. It’s also limited in its torque transfer ability by the coefficient of friction of the plastic Lego parts. Despite this, it’s a quick way to illustrate the mechanisms at play, and where some of the common losses are in such a system. If you prefer your gearboxes of a more classic sequential design, we’ve seen those too, of course. Video after the break.

source https://hackaday.com/2021/02/05/building-a-continuously-variable-transmission-with-lego/

If someone brought you an odd piece of electronic hardware and you wanted to identify it, you’d probably look for markings on the outside first. If that didn’t work out, you might look under the cover and read some markings on the board or key components. However, in a tough case, you might dump the firmware and try to guess what the device is or what it does by examining the code that makes it run. That’s kind of what [Ciro] did. Wanting to determine the bacteria in a water sample led to using relatively inexpensive DNA sequencing hardware to look at the DNA present in the samples. This would have been a huge undertaking for a well-funded lab just a few short years ago. Now it just takes a USB device and some software.

Of course, inexpensive is in the eye of the beholder. The micropore sequencer costs about $500 and has a one-time use consumable cost of about $500, although that’s enough to process about 10 human genomes. The technology depends on using a small pore only large enough to pass one strand of DNA at a time. Blocks of nucelotides cause different amounts of electrical current to flow through the pore.

A lot of blood cell counters work in a similar fashion, but have an easier mechanism as they look for the tiny aperture’s partial blockage. Determining which DNA components are passing through the pore requires very precise measurements.

Of course, such a thing is hardly plug and play. First, the water samples needed reduction using several filtration and separation techniques. Then a polymerase chain reaction clipped the part of the DNA that would allow for the identification of unique bacteria types. Truly, the work in concentrating the DNA samples seemed to dwarf the actual sequencing.

Honestly, we aren’t as knowledgeable about DNA science as we’d like to be, but we were impressed at the results you could get for less than you’d spend on a big PC. Polymerase chain reaction technology has become cheap and simple, maybe this is the next frontier on biohacking. We’ve looked at how you can get started with PCR several times.

source https://hackaday.com/2021/02/05/sequencing-dna-for-metagenomics/

The 20th century saw a great many cheap, utilitarian vehicles enter the marketplace. Cars like the Mini and the original Jeep offered low-cost, no-frills motoring. However, they were also decidedly low-tech, and not as reliable as modern cars by a long shot. The Citroën Mehari fits into this category neatly, and when [FVFILIPPETTI] grew tired of the unreliable points ignition system, he decided to build a more modern replacement.

The system is based around at ATmega328, the venerable chip many are familiar with from its starring role in the Arduino Uno. The chip tracks engine position with a magnet mounted on the flywheel combined with a hall-effect sensor, passed through an optocoupler to avoid nasty high-voltage spikes from the spark system interfering with the microcontroller. The chip then charges the ignition coil and fires it at the necessary time to ignite the air fuel mixture.

Old-school mechanical ignition systems were, if we’re honest, terrible compared to more modern solutions. This build has rewarded [FVFILIPPETTI] with a far more reliable ride, which we’re sure is very satisfying. If all this hacking has you thirsty for an automotive project of your own, dive into our primer on how to get into cars!

source https://hackaday.com/2021/02/05/custom-ignition-for-a-citroen-mehari/

While the de facto smartphone design ultimately went in a different direction, there’s no denying the classic BlackBerry layout offered some compelling advantages. It was a gadget primarily designed to send and receive emails and text messages, and it showed. So is it really any wonder [MSG] would build his pocket-sized LoRa messengers in its image?

Of course, he did have some help. The communicators use the Keyboard FeatherWing by [arturo182], which puts a surplus BlackBerry Q10 keyboard on a custom PCB designed to accept a board from Adafruit’s Feather collection. [MSG] ended up pairing his with a Feather M4 because he wanted to work with CircuitPython, with a 900 MHz LoRa FeatherWing along for the ride. He notes that switching his code over to Arduino-flavored C would allow him to use the Feather M0 that features integrated LoRa; a change that would allow him to make the gadget a bit thinner.

Inside the 3D printed enclosure, He’s made room for a 3.7 V 1800 mAh pouch battery that should provide plenty of runtime. There’s also an external antenna with a uFL pigtail for connecting to the radio. The case is held together with heat-set inserts, which should make it more than robust enough to handle a few adventures.

[MSG] says slight variations in hardware versions means his STLs might need a little tweaking to fit your components, and warns that his code is basically just a mashup of examples he found online, but he’s still sharing the goods for anyone who wants to reach out and touch someone without all that pesky infrastructure in the way.

source https://hackaday.com/2021/02/05/lora-messenger-does-its-best-blackberry-impression/

As [Luuk Esselbrugge] explains in a recent blog post, his 2002 Volvo S60 had an optional GPS navigation system and backup camera that used a motorized display that would rise out of the dashboard when needed. His particular car didn’t come with the hardware installed, but after getting his hands on a display module and doing some research, he figured out how he could drive it with the Raspberry Pi and a couple of microcontrollers.

Given the age of the display, you probably won’t be surprised to hear that it uses composite video. Not exactly high resolution, but in the demonstration after the break, we have to admit it looks more than up to the task. [Luuk] is running Android Auto on the Raspberry Pi 3 through the openauto project, which gives him a nice big display and access to all the navigation and media applications you’d expect. The display doesn’t support touch, but thanks to an ESP32 plugged into the CAN bus, he’s able to control the software by reading the buttons built into the Volvo’s steering wheel.

To actually raise and lower the display, [Luuk] found you just need to fire a few bytes down the 1,200 baud serial bus that’s built into the display’s wiring harness. The ESP32 handles this duty as well, at least partly because it’s already plugged into the CAN bus and can tell when the vehicle is in reverse. This lets it bring up the screen to show the video feed from the newly installed backup camera in the event that the Pi hadn’t already asked to raise the display. Incidentally plugging in the phone normally triggers the system to wake up and raise the screen, and disconnecting it will command the screen to lower back into the stowed position.

The attentive reader or Volvo aficionado may be wondering how [Luuk] got the audio working. Since his car’s sound system doesn’t feature an auxiliary input, he’s using an Arduino to spoof the existence of a CD changer, which allows him to inject an audio signal into one of the pins on the back of the radio. Eventually he wants to move this task over to the ESP32, but he says a big change like that will have to wait until warmer weather.

This isn’t the first time we’ve seen the Raspberry Pi used to add enhanced features to a somewhat older vehicle. While some bemoan the increased complexity of modern vehicles, it seems some hackers can’t get enough of it.

source https://hackaday.com/2021/02/05/raspberry-pi-takes-over-volvos-integrated-lcd/

One aspect of working for Hackaday comes in our regular need to take good quality photographs for publication. I have a semi-decent camera that turns my inept pointing and shooting into passably good images, but sometimes the easiest and quickest way to capture something is to pull out my mobile phone.

It’s a risky step because phone camera modules and lenses are tiny compared to their higher quality cousins, and sometimes the picture that looks good on the phone screen can look awful in a web browser. You quickly learn never to zoom on a mobile phone camera because it’s inevitably a digital zoom that simply delivers grainy interpolated pictures.

That’s not to say that the zoom can’t be useful. Recently I had some unexpected inspiration when using a smartphone camera as a magnifier to read the writing on a chip. I don’t need an archival copy of the image… I just needed a quick magnifying tool. Have I been carrying a capable magnifier for soldering in my pocket or handbag for years without realising it? I decided to give it a try and it worked okay with a few caveats. While I have seen optics turn these cameras into pretty good microscopes, my setup added nothing more than a phone tripod, and will get you by in a pinch.

What’s Your Magnifier Of Choice?

There was a time when I was much younger in which I remember being able to read the text on a SOT-23 transistor, but sadly even now wearing glasses those days are long past. Fortunately for me though I have a huge variety of options for soldering magnification. At various times I’ve used desktop magnifiers and headband magnifiers, but I’ve settled upon a large lens on an Anglepoise-style arm — you know, the springy lamp kind. These lens-on-an-arm are very common with beauty therapists and the like, utilizing a powerful ring of LED lights and providing ample magnification even for my eyes. I’ve also used various different LCD magnifiers belonging to friends and hackerspaces, but while I an extremely impressed by them I’ve so far been put off by the price for decent ones (even if I’ve brought you a super-cheap alternative via the unexpected medium of an ear cleaning camera in the past). My colleague Elliot meanwhile uses a very high quality 1970s binocular examination microscope that delivers exceptional quality, an instrument he swears by and which you will sometimes see being used in his work like the recent Raspberry Pi Pico review.

With all this very usable and capable equipment to hand it’s very clear that a mobile phone would have to be an exceptionally good alternative if it were to supplant them. But how about as a quick in-the-field option to sit alongside what you already have? Time to give it a try, and solder something with it.

Useful For More Than Cat Pictures? We give Our Phone A Try

The phones I had to hand were nothing special, the mid-range Huawei and Motorola Android devices that are my constant companions for both business and personal use. No high-end flagship cameras here, but the current generation of decent-ish phone cameras with which they gave similar results. I’m guessing that almost any smartphone made over the last few years could be pressed into service here. I put it on the mini tripod I use for Hackaday close-up shots, and pulled out a half-finished kit for a bit of soldering practice.

The image on maximum zoom provides plenty of magnification, and provides a high quality view of the work. In that context it’s better than my big magnifier, as it can deliver a closer view. The positive news ends though when the work starts, as a small but noticeable delay between action and screen leads to something of a learning curve as your soldering technique adapts. Perhaps more disconcerting is an unexpected disorientation in what I can only describe in perspective terms if that’s possible on a 2D display. These effects hold a fascination for me as someone who can’t see stereoscopic 3D, so why does a real 2D LCD microscope not have this problem? I am theorising when I say this, but I suspect that the solution lies in the camera’s depth of field. A mobile phone is designed to take reasonable pictures of everything in its field of view, so it has a particularly wide depth of field. The microscope meanwhile is designed to bring objects at a particular distance into sharp focus, so with its narrow depth of field it transmits some depth information in terms of focus. Our brains subconsciously process this, making depth placement of a soldering iron an easier process.

So I was able to solder a few components successfully through my phone’s view of the world. The slight delay and lack of perspective took a little getting around, and I can’t honestly recommend this technique for anybody’s bench. It does however remain a just-about-viable solution for impromptu SMD soldering in the field, but I’d advise you to practice a little before working on anything you care about. Perhaps a better bet would be to put one of those ear cameras I mentioned in your field toolkit alongside your miniature soldering iron, and use the mobile phone instead as its display. Everything is worth trying once, but perhaps a phone as an SMD soldering aid isn’t worth trying twice.

source https://hackaday.com/2021/02/05/using-your-phone-as-a-microscope-on-the-electronics-workbench/

Hackaday editors Elliot Williams and Mike Szczys spin the wheel of hardware hacking brilliance. We’re enamored with the quest for a root shell on a Nissan Xterra infotainment system, and smitten with a scanning microscope that uses a laser beam and precision positioning from DVD drives. We speculate on the future of artificial intelligence in the culinary arts. And this week turned up a clever way to monitor utility usage while only changing the battery on your sensor once per year.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (~65 MB)

Places to follow Hackaday podcasts:

• Google Podcasts
• iTunes
• Spotify
• Stitcher
• RSS

Episode 104 Show Notes:

New This Week:

• Elliot’s working on a rover with mechanum wheels

Interesting Hacks of the Week:

• Nissan Gives Up Root Shell Thanks To Hacked USB Drive
  • 32C3: Dieselgate — Inside The VW’s ECU
• DVD Optics Power This Scanning Laser Microscope
  • Take The Long Road To A Precise Laser PCB Exposer
• Youngster’s ESP32 Jukebox Uses RFID To Queue Tunes
• Giant DIY Mouse Sets The Ball Free
• Old Gas Meter Gets Smart With The ESP8266
• Logic Meter Aims To Make Hobby Electronics Troubleshooting Easier

Quick Hacks:

• Elliot’s Picks:
  • Serial Studio: Easily Visualise And Log Serial Data
  • Upgrading An Old MIG Welder Wire Feeder With Arduino
  • Handy Tool Drains 18650 Cells So You Don’t Have To
• Mike’s Picks:
  • An Op-Amp From The Ground Up
  • Learn Bil Herd’s DIY Surface Mount Assembly Process
  • How Does A Circuit Breaker Break?
    • Inside A Circuit Breaker With MikesElectricStuff

Can’t-Miss Articles:

• It Costs WHAT?! A Sounding Into Hearing Aids
  • What is a telecoil – and do all hearing aids have telecoils?
• Machine Learning In The Kitchen Makes For Tasty Mashup Desserts
  • [Ben Krasnow] Did It All For The (Perfect) Cookie

source https://hackaday.com/2021/02/05/hackaday-podcast-ep-104-delicous-ai-dvd-scanning-microscope-and-battery-friendly-microcontroller-designs/

One of the selling points of the Arduboy is how slim [Kevin Bates] was able to get the Arduino-compatible game system, which is perhaps less surprising when you realize that it originally started out as a design for an electronic business card. But compared to the recently unveiled Nano version, it might as well be the old school “brick” Game Boy.

Now to be clear, [Kevin] isn’t looking to put these into official production. Though it does sound like the bare PCBs might be going up for sale in the near future. This was simply an experiment to see how far he could shrink the core Arduboy hardware while still keeping it not only playable but also code-compatible with the full-size version. While “playable” might be a tad subjective in this case, the video after the break clearly demonstrates that it’s fully functional.

Inside the 3D printed case is the same ATmega32U4 that powers the Arduboy, a 64×32 0.49″ OLED display, and a tiny 25 mAh pouch battery. There’s even a miniature piezo speaker for the bleeps and bloops. All of the pinouts have remained the same so existing code can be moved right over, though the screen is now connected over I2C. [Kevin] has released the schematics for the board in keeping with the general open nature of the Arduboy project, though for now he’s decided to hold onto the board files until it’s clear whether or not there’s a commercial future for the Nano.

We’ve seen attempts to shrink the Arduboy down before, most notably down to the point it could fit inside of a Dreamcast Visual Memory Unit, but the Nano certainly raises (or is that lowers?) the bar considerably.

source https://hackaday.com/2021/02/05/arduboy-gets-even-smaller-with-new-nano-edition/

Perl has been stolen. Well, perl.com, at least. The perl.com domain was transferred to a different registrar on January 27, without the permission of the rightful owner. The first to notice the hack seems to have been [xtaran], who raised the alarm on a Reddit thread. The proper people quickly noticed, and started the process of getting control of the domain again. It seems that several other unrelated domains were also stolen in the same attack.

I’ve seen a couple of theories tossed around about how the domains were stolen. With multiple domains being moved, it initially seemed that the registrar had been compromised in some way. One of the other victims was told that a set of official looking documents had been supplied, “proving” that the attacker was the rightful owner of the domain. In any case, the damage is slowly being unwound. Perl.com is once again in the proper hands, evidenced by the proper SSL certificate issued back in December.

The Great Suspender, Suspended

I was greeted by a particularly nasty surprise on Thursday of this week. One of the Chrome extensions I’ve come to rely on was removed by Google for containing malware. The Great Suspender automatically hibernates unused tabs, saving ram and processor cycles that would otherwise be spent on those 150 open tabs that should really be bookmarks. What happened here?

I’ll point out that I’m extremely careful about installing extensions. It’s code written by a third party, often very difficult to inspect, and can view and modify the sites you visit. You can manage what sites an extension has access to, but for a tool like the Suspender, it essentially needs access to all of them. The solution is to use open source extensions, right? “Well yes, but actually no.” Suspender is open source, after all. The link above goes to the project’s Github page. In that repo you’ll find an announcement from last year, that the founding developer is finished with the project, and is selling the rights to an unknown third party, who took over maintainership. If this sounds familiar, there are echoes of the event-stream debacle.

It’s not clear exactly what malicious behavior Google found that led to the extension being pulled, but a more careful look at the project reveals that there were potential problems as early as October of 2020. An addition to the extension introduced execution of code from a remote server, never a good idea. For what it’s worth, the original maintainer has made a statement, defending the new owners, and suggesting that this was all an innocent mistake.

The lesson here? It’s not enough to confirm that an extension checks the “open source” box. Make sure there is an active community, and that there isn’t a 6 month old bug report detailing potentially malicious activity.

Libgcrypt

It’s not everyday you see a developer sending out a notice that everyone should stop using his latest release. That’s exactly what happened with Libgcrypt 1.9.0. Our friends over at Google’s Project Zero discovered an extremely nasty vulnerability in the code. It’s a buffer overflow that happens during the decryption process, before even signature verification. Since libgcrypt is used in many PGP implementations, the ramifications could be nasty. Receive an encrypted email, and as soon as your client decrypts it, code is executing. Thankfully, an update that fixes the issue has already been released.

Android Botnet

A new botnet is targeting Android devices in a peculiar way — looking for open ADB debug ports exposed to the Internet. Google makes it very clear that ADB over the network is insecure, and should only be used for development purposes, and on controlled networks. It’s astounding that so many vendors ship hardware with this service exposed. Beyond that, it’s surprising that so many people give their Android devices public IP addresses (or IPv6 addresses that aren’t behind a firewall). The botnet, named Matryosh, has another unique feature, as it uses Tor for command and control functions, making it harder to track.

Google Solution to Open-Source Security

Google published a post on their open source blog, giving an overview for their new framework for the security of open source projects. “Know, Prevent, Fix” is their name for the new effort, and it must have been written by management, because it’s full of buzzwords. The most interesting elements are their goals for critical software. They identify problems like the ability of a single maintainer to push bad code into a project, and how anonymous maintainers is probably a bad idea. It will be interesting to see how these ideas develop, and how Google will help open source communities implement them.

Microsoft in My Pi

And finally, I was amused by an article lamenting the inclusion of the VSCode repository in the default Raspberry Pi OS images. He does raise a couple legitimate points. Amont them, you do send a ping to Microsoft’s servers every time you check for new updates.

The larger point is that the official VSCode binaries have telemetry code added to them — code that isn’t in the open source repository. What is it doing? You don’t know. But it probably violates European law.

Want to use VSCode, but not interested in shipping info off to Microsoft? VSCodium is a thing.

source https://hackaday.com/2021/02/05/this-week-in-security-perl-com-the-great-suspender-and-googles-solution/

It may have been designed for a sewing machine, but [Haris Andrianakis] found his imported DC brushed motor was more than up to the challenge of powering his mini lathe. Of course there’s always room for improvement, so he set out to reverse engineer the motor’s controller to implement a few tweaks he had in mind. Unfortunately, things took an unexpected turn when plugging his AVR programmer into the board’s ISP socket not only released the dreaded Magic Smoke, but actually tripped the breaker and plunged his bench into darkness.

Upon closer inspection, it turned out the board has no isolation between the high voltage side and its digital logic. When [Haris] connected his computer to it via the programmer, the 330 VDC coming from the controller’s rectifier shorted through the USB bus and tripped the Earth-leakage circuit breaker (ELCB). The good news is that his computer survived the ordeal, and even the board itself seemed intact. But the shock must have been too much for the microcontroller he was attempting to interface with, as the controller no longer functioned.

Now fully committed, [Haris] started mapping out the rest of the controller section by section. In the write-up on his blog, he visually masks off the various areas of the PCB so readers have an easier time following along and understanding how the schematics relate to the physical board. It’s a nice touch, and a trick worth keeping in mind during your own reverse engineering adventures.

In the end, [Haris] seems to have a good handle on what the majority of the components are up to on the board. Which is good, since getting it working again now means replacing the MCU and writing new firmware from scratch. Or perhaps he’ll just take the lessons learned from this controller and spin up his own custom hardware. In either event, we’ll be keeping an eye out for his next post on the subject.

source https://hackaday.com/2021/02/05/motor-controller-reverse-engineering-releases-smoke/

Creating your own PC board is a rite of passage for many. These days, though, you can order super inexpensive boards and have them in very little time, so it doesn’t always make sense to build your own. Still, some people like the challenge, and others don’t want to wait even a few days. Probably everyone has dreamed of a 3D printer-like machine that would just crank out beautiful PCBs. The Voltera V-One isn’t quite at that level of sophistication, but it isn’t too far from it. [Great Scott] shows us how he built two different boards using the system in the video below. While the results were impressive, you can also see that there are several limitations, especially if you are not designing your board with the machine in mind.

One thing that is obvious is that the machine does need your help. In addition to aligning holes, you’ll need to install tiny rivets for vias and slightly less tiny rivets for through-hole components. The last time we looked at the machine, it didn’t do holes at all, but [Scott] shows the drill attachment which allows the machine to produce vias and support leaded components.

The system relies on interchangeable heads and conductive inks. Mechanically, it doesn’t differ much from a 3D printer. The ink, however, appears to be a little temperamental. On the first test board, one side did not cure properly since [Scott] forgot a step. While it looked fine, it had problems soldering. Because the traces are not copper, the machine comes with its own recommended solder, too.

The most interesting part, though, was when [Scott] tried to port an existing board into the system. He had to make several changes for things like copper fills and via hole sizes. Close spacing required some hand rework, so he probably should have spaced the traces wider in the design.

The printer isn’t cheap and the consumables are rather expensive, too. It is hard to justify the cost just to get fast prototypes that aren’t very representative of a final board. Keep in mind the conductive ink isn’t as conductive as copper and you don’t get niceties like solder mask or silk screening. If you had an active hacker space, a school, or a busy lab it might be worth it to get one-off boards. However, for prototyping production boards, it is unlikely that you’ll want to constrain your final design to the restrictions necessary for the printer. Besides, if you don’t mind waiting for boards — keeping in mind that you can pay to get boards made and shipped quickly if you don’t mind paying more — the breakeven point on the printer is very high.

On the other hand, 3D printers used to be expensive and now they are everywhere. The quality of 3D printing isn’t as good as some other production methods, but it still has a place. So if this technology improves a little and gets a lot cheaper, it could find its way to your workshop one day.

Back in 2015, we predicted that making your own PCBs was getting harder to justify. At the time, many people were unhappy with that prediction, but further decreases in the cost of having boards made for you continue to chip away at the value proposition of making your own boards. Sure, sometimes you just want to do something despite the economics — we’ve all done that. But it does make the economics of PCB printers even harder to work out.

source https://hackaday.com/2021/02/05/hands-on-with-the-voltera-v-one-pcb-printer/

It’s long been common wisdom that one of the safest places to keep your cryptocurrency holdings is in a hardware wallet. These are small, portable devices that encrypt your keys and offer a bit more piece of mind than holding your coins in a soft or web wallet.

But of course, as we know, nothing is totally secure.

And we were reminded of this fact by Kraken Security Labs, when they showed us how they bypassed all of the safeguards in a popular wallet, the Trezor, to dump and decrypt it’s seed.

It’s worth noting that the hack does require physical access to the wallet — albeit only about fifteen minutes worth. And by “physical access” we mean that the hack leaves the device thoroughly mutilated. The Kraken team started by desoldering the heart of the wallet, a STM32 processor. They then dropped it into a socket on an interface board, and got to glitching.

The hack relies on an attack known as voltage glitching. Essentially, at a precisely-timed moment during the device’s boot sequence, the supply voltage is fluctuated. This enables the chip’s factory bootloader, which can read out the contents of it’s onboard flash memory. The memory is read-protected, but can be accessed 256 bytes at a time through a second voltage glitch. Neither of these attacks work 100% of the time, so if the device fails to boot or the memory remains locked, the FPGA performing the attacks simply tries again. After enough iterations, the Kraken team was able to fully dump the chip’s flash memory.

There’s one more hurdle here —  the memory dump is encrypted. Enter brute forcing. Trezor devices allow a maximum pin code length of nine digits, but if you assume the average user’s pin is only four digits then it can be guessed via an automated script in a matter of minutes. Even a longer pin can be worked out in a matter of days or weeks — certainly within the realm of possibility. This yields the seed, which could then be entered into a new hardware wallet to effectively steal any cryptocurrency assets that lived on the original device.

So, aside from some cool hardware hacking techniques, what can we learn from the Kraken Security Lab’s work? First up, for any designers out there, the STM32 is not suitable for high-security applications. For all the end users, this doesn’t mean you need to trash your Trezor (even though this isn’t the first wallet hack we’ve seen). It does mean that you should keep it away from other people, and that you should enable the BIP39 passphrase, which Kraken says can protect against the attack. Perhaps most importantly, this serves to remind us all that nothing is 100% secure.

source https://hackaday.com/2021/02/04/hacking-hardware-bitcoin-wallets-extracting-the-cryptographic-seed-from-a-trezor/

It’s long been common wisdom that one of the safest places to keep your cryptocurrency holdings is in a hardware wallet. These are small, portable devices that encrypt your keys and offer a bit more piece of mind than holding your coins in a soft or web wallet.

But of course, as we know, nothing is totally secure.

And we were reminded of this fact by Kraken Security Labs, when they showed us how they bypassed all of the safeguards in a popular wallet, the Trezor, to dump and decrypt it’s seed.

It’s worth noting that the hack does require physical access to the wallet — albeit only about fifteen minutes worth. And by “physical access” we mean that the hack leaves the device thoroughly mutilated. The Kraken team started by desoldering the heart of the wallet, a STM32 processor. They then dropped it into a socket on an interface board, and got to glitching.

The hack relies on an attack known as voltage glitching. Essentially, at a precisely-timed moment during the device’s boot sequence, the supply voltage is fluctuated. This enables the chip’s factory bootloader, which can read out the contents of it’s onboard flash memory. The memory is read-protected, but can be accessed 256 bytes at a time through a second voltage glitch. Neither of these attacks work 100% of the time, so if the device fails to boot or the memory remains locked, the FPGA performing the attacks simply tries again. After enough iterations, the Kraken team was able to fully dump the chip’s flash memory.

There’s one more hurdle here —  the memory dump is encrypted. Enter brute forcing. Trezor devices allow a maximum pin code length of nine digits, but if you assume the average user’s pin is only four digits then it can be guessed via an automated script in a matter of minutes. Even a longer pin can be worked out in a matter of days or weeks — certainly within the realm of possibility. This yields the seed, which could then be entered into a new hardware wallet to effectively steal any cryptocurrency assets that lived on the original device.

So, aside from some cool hardware hacking techniques, what can we learn from the Kraken Security Lab’s work? First up, for any designers out there, the STM32 is not suitable for high-security applications. For all the end users, this doesn’t mean you need to trash your Trezor (even though this isn’t the first wallet hack we’ve seen). It does mean that you should keep it away from other people, and that you should enable the BIP39 passphrase, which Kraken says can protect against the attack. Perhaps most importantly, this serves to remind us all that nothing is 100% secure.

source https://hackaday.com/2021/02/04/hacking-hardware-bitcoin-wallets-extracting-the-cryptographic-seed-from-a-trezor/