TechyMagThings

Although modern-day silvered glass mirrors have pretty much destroyed the market for bronze mirrors, these highly polished pieces of metal once were the pinnacle of mirror technology. Due to the laborious process required these mirrors saw use essentially only by the affluent. That said, how hard would it be to make a bronze mirror today with all of the modern technologies that even a hobbyist can acquire for their shed? Cue [Lundgren Bronze Studios] giving it a shot, starting by casting something flat-ish to start polishing.

Just getting that initial shape to start polishing is a chore, with hammering out the shape possibly being also a viable method. When casting metal it’s tricky to avoid having air bubbles and other defects forming, though using a sand mold seems to help a lot.

After you have the rough shape, polishing using power tools seems like cheating, but as you can see in the video even going from 50 to 8000 grit with a rotating disc left countless scratches. Amusingly, hand sanding did a much better job of removing the worst scratches, following which a polishing compound helped to bring out that literal mirror finish.

A quick glance at the Wikipedia entry for bronze mirrors shows that a tin-bronze alloy like speculum metal was used for thousands of years as it was much easier to polish to a good mirror finish. The metallurgy of what may seem like just a vanity item clearly goes deeper than just polishing up a metal surface.

Cooking food with fire is arguably the technology that propelled humans to become the dominant species on Earth. It’s pretty straightforward to achieve, just requiring a fuel source, a supply of oxygen from the air, and a way to initiate the reaction; then it self-sustains. You wouldn’t think there’s much to improve, but what about cooking with plasma? [Jay] from the plasma channel is no stranger here, and he thinks that there may be something in this idea, certainly enough to actually build something.

Now, let’s be straight with you, this isn’t a new concept, and you can buy a plasma-based cooking appliance right now. But they are all AC-powered devices. What if you want to go camping? [Jay] attempts (and succeeds) in building a portable, rechargeable 600W plasma cooking device that can actually cook food, but it was not all plain sailing.

The existing off-the-shelf ZVS driver modules available were a bit weak and unreliable, and the required flyback coils were hard to find with the right specs, so he needed to get down to work building custom parts. First off, the coils. Custom formers were resin-printed and machine-wound with 4000 turns of fine wire, and then resin-sealed into the former. [Jay] takes care to explain that it is crucial to get all the air out of the windings, or else local flashover breakdown will occur and wreck the coil in a short time. We reckon the resulting coils look amazing in their own right!

Next, the ZVS drivers on hand had low-quality capacitors (well, not enough capacitance anyway) and cheap driver transistors, so both were upgraded. The initial plan was to have four driver/coil pairs, each driving a single pair of electrodes, with a common ground ring connecting them all. It turns out this was a terrible idea: the drivers were not synchronised, so they were pulling on each other, causing catastrophic damage to the PCBs in a very short time. The solution was more complicated wiring, to give each coil secondary output a dedicated electrode pair, so there was no direct electrical connection between neighbouring coils and no coupling between them. A clever electrode arrangement meant that a pan would sit on top of a ring of electrodes, causing plasma discharges to jump directly to the pan, thereby concentrating localised heating there. We were wondering how this new direct connection (the pan is now a common connection!) didn’t also cause backfeeding and kill the ZVS drivers again, but it didn’t seem to happen.

Anyway, [Jay] demonstrates what is possibly the world’s first rechargeable, portable plasma cooker capable of making breakfast. Which we think is very important in its own right, however, we would like a plasma-based solution to making toast next, perhaps a plasma knife that cooks the bread as you slice it?

If this plasma cooking lark rings a bell, yes, we did touch upon this way back in 2017. And whilst not strictly plasma cooking, you can make an amazing microwave plasma in this ridiculously upgraded appliance. Definitely do not try that one at home.

That boiling water is a contentious topic of discussion is clear, but what about hot air? When you take a 12 VDC, 280 Watt-rated air fryer and pit it against a bog-standard 240 VAC, 1400 Watt unit, which one would you want to use when you’re doing some camping or other exciting off-the-grid opportunities? Unlike with boiling water the physics aren’t as clear-cut here, so [Cahn] did some testing to figure out exactly what the efficiency numbers look like

Since air fryers rely on the transfer of thermal energy from the resistive heating element into the food, any thermal energy that’s not immediately transferred is effectively wasted. This, combined with the relatively low power rating and thus much higher time demand of the low-voltage air fryer is enough to set one’s expectations pretty low.

As scientific test samples chicken nuggets were used with the test, following a preheating period for the 12 VDC unit. Both units managed to hit a safe temperature inside the nuggets after 20 minutes, thus successfully staving off food poisoning, but the browning with the 240 VAC air fryer was much better.

As for the efficiency, the 12 VDC unit required 150 Wh for 20 minutes plus the 10 minutes of preheating, with 45 minutes total at 225 Watt to get proper browning. Meanwhile the 240 VAC unit burned through 250 Wh in 20 minutes, with no pre-heating, though only 230 Wh with no inverter losses included. As a final test, the 12 VDC unit was run at 400 Watt using 14.6 VDC input, which did indeed get it up to temperature much faster.

Thus both are equivalent, just with the caveat that the low-voltage unit will take considerably more time to get the same result. This mirrors the results with boiling water, where most options mostly vary in how much time they require to get water up to a boiling temperature.

It’s fair to say that there are a lot of development board form factors for MCUs, with [Tech Dregs] over on yonder YouTube on the verge of adding another one to the pile, but not before he was having some serious thoughts on the implications of such a decision. Does this world really need another devboard with the ubiquitous 2.54 mm (0.1″) pitch pin headers, all so that it can perhaps be used in the same traditional 2.54 mm pitch breadboards?

The thought that [Tech Dregs] is playing with is to go for something more akin to the system-on-module  (SoM) approach that’s reminiscent of the Raspberry Pi compute module form factor. This means using a 1 mm pitch for the headers and castellated edges in case you want use it as an SMT part, while breaking out many more pins of the onboard ESP32 module in far less space.

Obviously, the main advantage of this approach is that much like with compute modules you can leave most of the tedious cheap stuff on a carrier board, while the expensive to manufacture components are on a self-contained module. Meanwhile with the much finer pitch on the SoM contacts it’d straddle the divide between a 2.54 mm breadboard-capable devboard and a fully custom PCB, while making any mistakes on the carrier board much cheaper to redo.

The counterpoint here is of course that something like an ESP32 module is already a module with a finer pitch, but if you need more than just what it offers, or you want to use an STM32 or RP MCU across boards it could make a lot of sense.

Having 1 mm pitch breadboards would honestly also be rather nifty, natch. That said, what are your thoughts on this matter?

Oscilloscopes and to lesser extent signals generators are useful tools for analyzing, testing and diagnosing circuits but we often take for granted how they work. Luckily, [FromConceptToCircuit] is here to show us how they’re made.

[FromConceptToCircuit] starts by selecting the hardware to use: an Artix-7-based FPGA and an FT2232 USB-serial converter. RS245 in synchronous FIFO mode is selected for its high bandwidth of about 400 Mbps. Then, they show how to wire it all up to your FPGA of choice. Now it’s time for the implementation; they go over how the FT2232 interfaces with the FPGA, going through the Verilog code step-by-step to show how the FPGA makes use of the link, building up from the basic transmission logic all the way up to a simple framed protocol with CRC8-based error detection. With all that, the FPGA can now send captured samples to the PC over USB.

Now it’s PC-side time! [FromConceptToCircuit] first explains the physical pipeline through which the samples reach the PC: FPGA captures, transmits over RS245, FT2232 interfaces that with USB and finally, the software talks with the FT2232 over USB to get the data back out. The software starts by configuring the FT2232 into RS245 mode, sets buffer sizes, the whole deal. With everything set up, [FromConceptToCircuit] explains how to use the FT2232 driver’s API for non-blocking communication.

As a bonus, [FromConceptToCircuit] adds a signal generator feature to the oscilloscope using an I2C DAC chip. They start by explaining what exactly the DAC does and follow up with how it’ll be integrated into the existing system. Then it’s time to explain how to implement the I2C protocol bit-for-bit. Finally combine everything together for one final demo that shows a sine wave on the DAC’s output.

While it might seem quaint these days, we’ve met many makers and hackers who reach for a pen and a pad when learning something new or working their way through some technical problem. But even if you’re the type of person who thinks best when writing something out on paper, there’s still a good chance that you’ll eventually want to bring those notes and sketches into the digital realm. That’s where things can get a little tricky.

[Spencer Adams-Rand] recently wrote in with his clever solution for capturing written notes and pushing them into Notion, but the hardware design and digitization workflow is flexible enough that it could be adapted to your specific needs — especially since he was good enough to release all the files required to build your own version.

Whether they are hand-written notes, old photographs, or legal documents, digitization boils down to taking a high resolution digital photo of the object and running it through the appropriate software. But getting good and consistent photos is the key, especially when you’re working your way through a lot of pages. [Spencer] started out just snapping pictures with his phone, but quickly found the process was less than ideal.

His custom scanning station addresses that first part of the problem: getting consistent shots. The images are captured using a Raspberry Pi 5 with attached Camera Module 3, while the 3D printed structure of the device makes sure that the camera and integrated lighting system are always in the same position. All he needs to do is place his notepad inside the cavity, hit the button, and it produces a perfect shot of the page.

Using a dedicated digitizing station like this would already provide better results than trying to freehand it with your phone or camera, but [Spencer] took things quite a bit farther. The software side of the project puts a handy user interface on the 5 inch touch screen built into the top of the scanner, while also providing niceties like a REST API and integration with the OpenAI Vision API for optical character recognition (OCR).

Those with an aversion to AI could certainly swap this out for something open source like Tesseract, but [Spencer] notes that not only is OpenAI’s OCR better at reading his handwriting, it spits out structured markdown-like data that’s easier to parse. From there it goes into the Notion API, but again, this could be replaced with whatever you use to collect your digital thoughts.

A device like this would go a long way towards answering a question we posed to the community back in January about the best way to digitize your documents.

Ever since it was called OpenBeOS, Haiku has targeted the x86 platform. That makes good sense: it’s hard enough maintaining a niche system on ubiquitous hardware. But x86 isn’t the only game in town anymore. Apple’s doing very well on ARM, Linux runs on oodles of ARM SBCs, and even Windows uh, exists, on that architecture, so why not Haiku? That’s what [smrobtzz] figured, and thanks to his work you can now run Haiku on ARM, in QEMU.

There’s no image available as yet — you still need to bootstrap your own from a working system, and ironically that system cannot be Haiku. [smrobtzz] apparently used MacOS, which makes sense as his ultimate goal is apparently to go where only Aishi Linux has gone before and boot Haiku on his M1 MacBook. There had been previous efforts to get Haiku going on Raspberry Pi hardware, which seems logical considering how lightweight the operating system is, but they’re apparently nowhere near booting either. QEMU is a good start.

Interestingly, according to the ports page, Haiku is “functional” on both RISC V QEMU and the now-discontinued HiFive Unmatched SBC. We don’t seem to have covered it, but that milestone happened five year ago. Given how most RISC V boards currently available are a bit slow for modern desktop Linux, Haiku would likely be a breath of fresh air. The BeOS-descended system might be single user, but it’s snappy.

We reported a couple of years back that Haiku was daily-drivable on x86 ,it’s only gotten better since then, assuming you choose the right hardware. Hardware support is always the hard part about alternative OSes, but Haiku users are absolutely spoiled compared to fans of MorphOS, which still only runs on G4 or G5 PowerPC, and even then not only some hardware.