Inside Digital Image Chips

Have you ever thought how amazing it is that every bit of DRAM in your computer requires a teeny tiny capacitor? A 16 GB DRAM has 128 billion little capacitors, one for each bit. However, that’s not the only densely-packed IC you probably use daily. The other one is the image sensor in your camera, which is probably in your phone. The ICs have a tremendous number of tiny silicon photosensors, and [Asianometry] explains how they work in the video you can see below.

The story starts way back in the 1800s when Hertz noticed that light could knock electrons out of their normal orbits. He couldn’t explain exactly what was happening, especially since the light intensity didn’t correlate to the energy of the electrons, only the number of them. It took Einstein to figure out what was going on, and early devices that used the principle were photomultiplier tubes, which are extremely sensitive. However, they were bulky, and an array of even dozens of them would be gigantic.

Semiconductor devices use silicon. Bell Labs was working on bubble memory, which was a way of creating memory that was never very popular. However, as a byproduct, the researchers realized that moving charges around for memory could also move around charges from photosensitive diodes. The key idea was that it was harder to connect many photodiodes than it was to create the photodiodes. Using the charge-coupled device or CCD method, the chip could manipulate the charges to reduce the number of connections to the chip.

CCDs opened up the digital image market, but it has some problems. The next stage was CMOS chips. They’d been around for a while since IBM produced the scanistor, but the sensitivity of these CMOS image chips was poor. Since most people were happy with CCD, there wasn’t as much research on CMOS. However, CMOS sensors would eventually become more capable, and the video explains how it works.

We’ve looked at image sensors before, too. The way you read them can make a big difference in your images.

Continue reading “Inside Digital Image Chips”

How Much Programming Can ChatGPT Really Do?

By now we’ve all seen articles where the entire copy has been written by ChatGPT. It’s essentially a trope of its own at this point, so we will start out by assuring you that this article is being written by a human. AI tools do seem poised to be extremely disruptive to certain industries, though, but this doesn’t necessarily have to be a bad thing as long as they continue to be viewed as tools, rather than direct replacements. ChatGPT can be used to assist in plenty of tasks, and can help augment processes like programming (rather than becoming the programmer itself), and this article shows a few examples of what it might be used for.

AI comments are better than nothing…probably.

While it can write some programs on its own, in some cases quite capably, for specialized or complex tasks it might not be quite up to the challenge yet. It will often appear extremely confident in its solutions even if it’s providing poor or false information, though, but that doesn’t mean it can’t or shouldn’t be used at all.

The article goes over a few of the ways it can function more as an assistant than a programmer, including generating filler content for something like an SQL database, converting data from one format to another, converting programs from one language to another, and even help with a program’s debugging process.

Some other things that ChatGPT can be used for that we’ve been able to come up with include asking for recommendations for libraries we didn’t know existed, as well as asking for music recommendations to play in the background while working. Tools like these are extremely impressive, and while they likely aren’t taking over anyone’s job right now, that might not always be the case.

Gordon Moore, 1929 — 2023

The news emerged yesterday that Gordon Moore, semiconductor pioneer, one of the founders of both Fairchild Semiconductor and Intel, and the originator of the famous Moore’s Law, has died. His continuing influence over all aspects of the technology which makes our hardware world cannot be overstated, and his legacy will remain with us for many decades to come.

A member of the so-called “Traitorous Eight” who left Shockley Semiconductor in 1957 to form Fairchild Semiconductor, he and his cohort laid the seeds for what became Silicon Valley and the numerous companies, technologies, and products which have flowed from that. His name is probably most familiar to us through “Moore’s Law,” the rate of semiconductor development he first postulated in 1965 and revisited a decade later, that establishes a doubling of integrated circuit component density every two years. It’s a law that has seemed near its end multiple times over the decades since, but successive advancements in semiconductor fabrication technology have arrived in time to maintain it. Whether it will continue to hold from the early 2020s onwards remains a hotly contested topic, but we’re guessing its days aren’t quite over yet.

Perhaps Silicon Valley doesn’t hold the place in might once have in the world of semiconductors, as Uber-for-cats app startups vie for attention and other semiconductor design hubs worldwide steal its thunder. But it’s difficult to find a piece of electronic technology, whether it was designed in Mountain View, Cambridge, Shenzhen, or wherever, that doesn’t have Gordon Moore and the rest of those Fairchild founders in its DNA somewhere. Our world is richer for their work, and that’s what we’ll remember Gordon Moore for.

You can read our thoughts on Moore’s famous law. If you ever wondered how Silicon Valley became the place for electronics, the story is probably much older than you think.

A LEGO Camera You Just Might Own Yourself

A camera makes for an interesting build for anyone, because it’s an extremely accessible technology that can be made from materials as simple as cardboard. More robust cameras often require significant work, but what if you could make a usable camera from LEGO? It’s a project taken on by [Zung92], who hasn’t simply made a working 35 mm camera from everyone’s favorite construction toy — he’s also managed to make it exude retro style. Best of all, you can vote for it on the LEGO Ideas website, and you might even get the chance to have one for yourself.

Frustratingly there’s little in the way of in-depth technical detail on the Ideas website, but he does mention that it was a challenge to make it light proof. Even the lens is a LEGO part, and if diffraction-based photography isn’t for you there’s also a pinhole option. We look forward to seeing this camera progress, and we hope we’ll see it advance to becoming a LEGO Ideas kit.

This is an extremely polished design, but surprisingly, it’s not our first LEGO camera.

Thanks [Michael] for the tip.

Clever Mechanism Powers This All-Mechanical Filament Respooler

No matter how far down the 3D printing rabbit hole we descend, chances are pretty good that most of us won’t ever need to move filament from one spool to another. But even so, you’ve got to respect this purely mechanical filament respooler design, and you may want to build one for yourself just because.

We were tipped off to [Miklos Kiszely]’s respooler via the very enthusiastic video below from [Bryan Vines] at the BV3D YouTube channel. He explains the need for transferring filament to another spool as stemming from the switch by some filament manufacturers to cardboard spools for environmental reasons. Sadly, these spools tend to shed fibrous debris that can clog mechanisms; transferring filament to a plastic spool can help mitigate that problem.

The engineering that [Miklos] put into his respooler design is pretty amazing. Bearings excepted, the whole thing is 3D printed. A transmission made of herringbone gears powers both the take-up spool and the filament guide, which moves the incoming filament across the width of the spool for even layers. The mechanism to do this is fascinating, consisting of a sector gear with racks on either side. The racks are alternately engaged by the sector gear, moving a PTFE filament guide tube back and forth to create even layers on the takeup spool. Genius!

Hats off to [Miklos] on this clever design, and for the extremely detailed instructions for printing and building one of your own. Even if you don’t have the cardboard problem, maybe this would help if you buy filament on really big spools and need to rewind for printing. Continue reading “Clever Mechanism Powers This All-Mechanical Filament Respooler”

Digitizing Sound On An Unmodified Sinclair ZX81

Whatever the first computer you used to manipulate digital audio was, the chances are it came with dedicated sound hardware that could play, and probably record, digitized audio. Perhaps it might have been a Commodore Amiga, or maybe a PC with a Sound Blaster. If you happen to be [NICKMANN] though, you can lay claim to the honor of doing so on a machine with no such hardware, because he managed it on an unmodified Sinclair ZX81.

For those of you unfamiliar with the ZX, it embodied Clive Sinclair’s usual blend of inflated promises on minimal hardware and came with the very minimum required to generate a black-and-white TV picture from a Zilog Z80 microprocessor. All it had in the way of built-in expansion was a cassette interface, 1-bit read and write ports exposed as 3.5 mm jacks on its side. It’s these that in an impressive feat of hackery he managed to use as a 1-bit sampler with some Z80 assembler code, capturing a few seconds of exceptionally low quality audio in an ’81 with the plug-in 16k RAM upgrade.

From 2023 of course, it’s about as awful as audio sampling gets, but in 1980s terms it’s pulling off an almost impossible feat that when we tried it with a 1-bit PC speaker a few years later, we didn’t succeed at. We’re impressed.

The ’81 may be one of the simplest of the 8-bit crop, but in its day it set many a future software developer on their career path. It’s still a machine that appears here today, from time to time.

Picture of the miniJen structure on a presentation desk

A Jenkins Demo Stand For Modern Times

Once you’re working on large-scale software projects, automation is a lifesaver, and Jenkins is a strong player in open-source automation – be it software builds, automated testing or deploying onto your servers. Naturally, it’s historically been developed with x86 infrastructure in mind, and let’s be fair, x86 is getting old. [poddingue], a hacker and a Jenkins contributor, demonstrates that Jenkins keeps up with the times, with a hardware demo stand called miniJen, that has Jenkins run on three non-x86 architectures – arm8v (aarch64), armv7l and RISC-V.

There’s four SBCs of different architectures involved in this, three acting as Jenkins agents executing tasks, and one acting as a controller, all powered with a big desktop PSU from Pine64. The controller’s got a bit beefier CPU for a reason – at FOSDEM, we’ve seen it drive a separate display with a Jenkins dashboard. It’s very much a complete demo for its purpose, and definitely an eyecatcher for FOSDEM attendees passing by the desk! As a bonus, there’s also a fascinating blog post about how [poddingue] got to running Jenkins on RISC-V in particular.

Even software demonstrations get better with hardware, and this stood out no doubt! Looking to build a similar demo, or wondering how it came together? [poddingue] has blog posts on the demo’s structure, a repo with OpenSCAD files, and a trove of videos demonstrating the planning, design and setup process. As it goes with continuous integrations, we’ve generally seen hackers and Jenkins collide when it comes to build failure alerts, from rotating warning lights to stack lights to a Christmas tree; however, we’ve also seen a hacker use it to keep their firmware size under control between code changes. And, if you’re wondering what continuous integration holds for you, here’s our hacker-oriented deep dive.