Sometimes, finding new ways to use old hardware requires awesome feats of reverse engineering, software sleight of hand, and a healthy dose of good fortune. Other times, though, it’s just as simple as reading the data sheet and paying attention to details.
Not that we’re knocking [upir]’s accomplishment with these tricked-out 16×2 OLED displays. Far from it, in fact — the smoothly animated bar graph displays alphanumerics look fantastic. What’s cool about this is that he accomplished all this without resorting to custom characters. We’ve seen him use this approach before; this time around, the hack involves carefully shopping for a 16×2 OLED display with the right driver chip — a US2066 chip. You’ll still need a few tricks to get things working, like extra pull-up resistors to get the I2C display talking to an Arduino, plus a little luck that you got a display with the right character ROM.
Once all that is taken care of, getting the display to do what you want is mainly a matter of coding. In the video below, [upir] does a great job of walking through the finer points, and the results look great. The bar graphs in particular look fantastic, with silky-smooth animations.
In the days of CRT displays, the precise synchronization between source and display meant that the time between a video line appearing at the input and the dot writing it to the screen was constant, and very small. Today’s display technologies deliver unimaginable resolutions compared to the TV your family had in the 1970s, but they do so at the expense of all their signal processing imposing a much longer delay before a frame is displayed. This can become an issue for gamers, but also with normal viewing, because in some circumstances the delay can be long enough for it to be audible in a disconnect between film and soundtrack. It’s something [Mike Kibbel] has addressed with his video input delay meter, and it makes for a very interesting project.
At its heart is an FPGA, and in the video below the break he goes into great detail about its programming. It both generates a DVI output to drive the monitor and performs the measurement. The analog to digital converter side of the circuit is interesting, he has a photodiode and an op-amp driving a comparator to form a simple 1-bit converter. He takes us through the design process in detail, with such useful little gems as the small amount of hysteresis applied to the comparator.
There are probably many ways this project could have been implemented, but this one is both technically elegant and extremely well documented. Definitely worth a look!
Hydrogen is a useful gas. Whether you want to float an airship, fuel a truck, or heat an industrial process, hydrogen can do the job. However, producing it is currently a fraught issue. While it can be produced cleanly using renewable energy, it’s often much cheaper to split it out of hydrocarbon fuels using processes that generate significant pollution.
If there’s an unsung hero of manufacturing, it’s the engineer who figures out how to handle huge numbers of small parts. It’s one thing to manually assemble something, picking each nut, bolt, and washer by hand. It’s another thing to build a machine that can do the same thing, but thousands of times in a row, ideally without making mistakes.
Most of us don’t need that level of automation in our processes, but when you do, it results in some interesting challenges. Take this pneumatic screw accelerator that [Christopher Helmke] designed for his modular production system. One of the custom machines in his system is a screw counter, which uses a magnetic wheel to feed screws — or nuts or washers — from a hopper, orient them correctly, and drop them into an output chute. While the counting bit worked quite well, parts would only go so far under the force of gravity in the clear vinyl tube used to connect the counter to the next process.
[Christopher]’s solution was simple but effective. His first prototype simply injects compressed air into the parts feed tube, which pushes the screws through the tubing. It works surprisingly well, propelling the parts through quite a long length of tubing, handling twisting paths easily and even working against gravity. Version 2 integrated the accelerator and a re-orienting fixture into a single part, which mates with a magazine that holds a large number of screws.
There are a lot of interesting features [Christoper] built into these simple parts that are worth keeping in mind. Our favorite is printing channels to guide small cable ties around the tubing to clamp it into the accelerator. We’ll be keeping that trick in mind.
From the early days of ARPANET until the dawn of the World Wide Web (WWW), the internet was primarily the domain of researchers, teachers and students, with hobbyists running their own BBS servers you could dial into, yet not connected to the internet. Pitched in 1989 by Tim Berners-Lee while working at CERN, the WWW was intended as an information management system that’d provide standardized access to information using HTTP as the transfer protocol and HTML and later CSS to create formatted documents inspired by the SGML standard. Even better, it allowed for WWW forums and personal websites to begin to pop up, enabling the eternal joy of web rings, animated GIFs and forums on any conceivable topic.
During the early 90s, as the newly opened WWW began to gain traction with the public, the Mosaic browser formed the backbone of the WWW browsers (‘web browsers’) of the time, including Internet Explorer – which licensed the Mosaic code – and the Mosaic-based Netscape Navigator. With the WWW standards set by the – Berners-Lee-founded – World Wide Web Consortium (W3C), the stage appeared to be set for an open and fair playing field for all. What we got instead was the brawl referred to as the ‘browser wars‘, which – although changed – continues to this day.
Today it isn’t Microsoft’s Internet Explorer that’s ruling the WWW while setting the course for new web standards, but instead we have Google’s Chrome browser partying like it’s the early 2000s and it’s wearing an IE mask. With former competitors like Opera and Microsoft having switched to the Chromium browser engine that underlies Chrome, what does this tell us about the chances for alternative browsers and the future of the WWW?
Over the years here at Hackaday, we’ve covered a range of stories about the ongoing panic surrounding drone flights. From plastic bags reported as drone incidents through to airports closed with no evidence of drones being involved, it’s clear that drone fliers are an embattled group facing a legal and aeronautical establishment that seems to understand little about them or their craft.
It sometimes seems to be a no-win situation for fliers, but perhaps [XJet] has something which might improve matters. He’s published a video showing off a portable ADS-B receiver which could be used by drone pilots to check for any aircraft in the vicinity and perhaps more importantly allow the drone community to take the moral high ground when problems occur.
The receiver isn’t particularly special, being a Raspberry Pi with LCD screen and an RTL-SDR receiver in a nice 3D printed enclosure. He says he’ll be publishing all software and build details in due course. But it’s the accessibility which makes it such a good idea, instead of being a very expensive safety device it’s a receiver that could probably be made with a less powerful Pi for under $100.
There is of course a flaw in the plan, that not all pilots are concerned enough for their safety to fit an ADS-B transponder to their aircraft, and so are invisible to both the thus-equipped drone pilot and air traffic control alike. This puts the onus on pilots to consider ADS-B an essential, but from the drone flier’s point of view we’d consider that a spotter should be part of their group anyway.
Ask anyone to name a first-generation home computer from the 1970s, and they’ll probably mention the likes of the Altair 8800 and IMSAI 8080. But those iconic machines weren’t the only options available to hobbyists back in the day: Heathkit, famous for its extensive range of electronic devices sold in kit form, jumped on the microcomputer bandwagon with their H8. Though it always remained a bit of an obscure machine, several dedicated enthusiasts kept making H8-compatible hardware and software long after the computer itself went out of production. That tradition continues in 2023, with [Scott M. Baker] producing a brand-new DRAM board that’s compatible with any version of the H8.
Although the Heathkit H8 was designed around the Intel 8080 processor, it could also be equipped with a Z80. [Scott] had built an 8085 based CPU board as well, meaning that any other hardware he developed for the H8 had to support these three processors. For something as timing-critical as a memory board, this turned out to be way harder than he’d expected.
First off, he had already made things difficult for himself by choosing DRAM rather than the simpler SRAM. Whereas SRAM chips can be more or less directly hooked up to the CPU’s address and data buses, a DRAM setup needs refresh circuitry to ensure the data doesn’t leak out of the chips’ internal capacitors. [Scott] decided to use the classic D8203 DRAM controller to do that for him — a solution that was pretty common back in the day.
Getting the timing right for all signals between the CPU and the DRAM controller was not at all trivial, however. The main problem was with two signals, called /SACK and /XACK, which were used to pause memory access during refresh cycles. Depending on which CPU was on the other side, these signals apparently had to be combined with other signals, stored in a flip-flop or delayed by a cycle or two in order to align with the processor’s internal logic. None of this seemed to work reliably, so [Scott] looked elsewhere for inspiration.
Luckily, traces are easy to follow on a two-layer board.
He found this on eBay, where a few vintage H8-compatible DRAM boards were for sale. Although [Scott] didn’t manage to win the auction, the eventual buyer was kind enough to snap some high-resolution pictures of the board which enabled him to reverse-engineer the circuit. The board used the similar D8202 DRAM controller and came with logic that generated the proper signals to interface with the 8080 and 8085 CPUs. For the Z80, [Scott] dived into the documentation for Heathkit’s Z80 option and found a schematic with a few logic gates that would satisfy the Zilog chip as well.
[Scott] combined both of these solutions on a beautiful 1980s-style printed circuit board, with a bunch of 7400 series logic gates and even two GAL22V10 programmable logic devices. With full documentation and Gerber files available on the project’s GitHub page, Heathkit H8 owners can now get their own brand-new memory board — in kit form, as a Heathkit should be.
