Wet Country Wireless; How The British Weather Killed A Billion Pound Tech Company

A dingy and cold early February in a small British town during a pandemic lockdown is not the nicest time and place to take your exercise, but for me it has revived a forgotten memory and an interesting tale of a technology that promised a lot but delivered little. Walking through an early-1990s housing development that sprawled across the side of a hill, I noticed a couple of houses with odd antennas. Alongside the usual UHF Yagis for TV reception were small encapsulated microwave arrays about the size of a biscuit tin. Any unusual antenna piques my interest but in this case, though they are certainly unusual, I knew immediately what they were. What’s more, a much younger me really wanted one, and only didn’t sign up because their service wasn’t available where I lived.

All The Promise…

The TV advert looked promising in 1998.
The TV advert looked promising in 1998.

Ionica was a product of Cambridge University’s enterprise incubator, formed at the start of the 1990s with the aim of being the first to provide an effective alternative to the monopolistic British Telecom in the local loop. Which is to say that in the UK at the time the only way to get a home telephone line was to go through BT because they owned all the telephone wires, and it was Ionica’s plan to change all that by supplying home telephone services via microwave links.

Their offering would be cheaper than BT’s at the socket because no cable infrastructure would be required, and they would aim to beat the monopoly on call costs too. For a few years in the mid 1990s they were the darling of the UK tech investment world, with a cutting edge prestige office building just outside Cambridge, and TV adverts to garner interest in their product. The service launched in a few British towns and cities, and then almost overnight they found themselves in financial trouble and were gone. After their demise at the end of 1998 the service was continued for a short while, but by the end of the decade it was all over. Just what exactly happened?

Continue reading “Wet Country Wireless; How The British Weather Killed A Billion Pound Tech Company”

The Vibrating Reed Inverter: Possibly The Simplest Inverter You Can Make

Those of us who work on the road have a constant dread of being stuck somewhere without power, facing a race between a publication deadline and a fast-failing laptop battery. We’re extremely fortunate then to live in an age in which a cheap, lightweight, and efficient solid-state switch-mode inverter can give us mains power from a car cigarette lighter socket and save the day. Before these inverters came much heavier devices whose transistors switched at the 50Hz line speed, and before them came electromechanical devices such as the rotary converter or the vibrating reed inverter. It’s this last type that [Robert Murray-Smith] has taken a look at, making what he positions as the simplest inverter that it’s possible.

If you’ve ever played with relays, you’ll probably be aware that a relay can be wired as a buzzer, and it’s this property that a vibrating reed inverter harnesses. He takes an octal relay and wires it up with a small mains transformer for an immediate and very cheap inverter. It’s not perfect, as he points out the frequency isn’t right. The relay will eventually wear out unless the arcing problem is improved with the addition of a capacitor. But it does make a rough and ready inverter if you find yourself in a MacGyver-style tight spot with only your junk box for salvation.

If inverters pique your interest, it might benefit you to know how they work.

Continue reading “The Vibrating Reed Inverter: Possibly The Simplest Inverter You Can Make”

NVMe Boot Finally Comes To The Pi Compute Module 4

Since the introduction of the Raspberry Pi Compute Module 4, power users have wanted to use NVMe drives with the diminutive ARM board. While it was always possible to get one plugged in through an adapter on the IO Board, it was a bit too awkward for serious use. But as [Jeff Geerling] recently discussed on his blog, we’re not only starting to see CM4 carrier boards with full-size M.2 slots onboard, but the Raspberry Pi Foundation has unveiled beta support for booting from these speedy storage devices.

The MirkoPC board that [Jeff] looks at is certainly impressive on its own. Even if you don’t feel like jumping through the hoops necessary to actually boot to NVMe, the fact that you can simply plug in a standard drive and use it for mass storage is a big advantage. But the board also breaks out pretty much any I/O you could possibly want from the CM4, and even includes some of its own niceties like an RTC module and I2S DAC with a high-quality headphone amplifier.

Once the NVMe drive is safely nestled into position and you’ve updated to the beta bootloader, you can say goodbye to SD cards. But don’t get too excited just yet. Somewhat surprisingly, [Jeff] finds that booting from the NVMe drive is no faster than the SD card. That said, actually loading programs and other day-to-day tasks are far snappier once the system gets up and running. Perhaps the boot time can be improved with future tweaks, but honestly, the ~7 seconds it currently takes to start up the CM4 hardly seems excessive.

NVMe drives are exciting pieces of tech, and it’s good to see more single-board computers support it. While it might not help your CM4 boot any faster, it definitely offers a nice kick in performance across the board and expands what the system is capable of. Continue reading “NVMe Boot Finally Comes To The Pi Compute Module 4”

Triton AR Headset Blends Stock And Printed Parts

Augmented reality (AR) and natural gesture input provide a tantalizing glimpse at what human-computer interfaces may look like in the future, but at this point, the technology hasn’t seen much adoption within the open source community. Though to be fair, it seems like the big commercial players aren’t faring much better so far. You could make the case that the biggest roadblock, beyond the general lack of software this early in the game, is access to an open and affordable augmented reality headset.

Which is precisely why [Graham Atlee] has developed the Triton. This Creative Commons licensed headset combines commercial off-the-shelf components with 3D printed parts to provide a capable AR experience at a hacker-friendly price. By printing your own parts and ordering the components from AliExpress, basic AR functionality should cost you $150 to $200 USD. If you want to add gesture support you’ll need to add a Leap Motion to your bill of materials, but even still, it’s a solid deal.

Exploded view of the Triton

The trick here is that [Graham] is using the reflectors from a surprisingly cheap AR headset designed to work with a smartphone. By combining these mass produced optics with a six inch 1440 x 2560 LCD panel inside of the Triton’s 3D printed structure, projecting high quality images over the user’s field of view is far simpler than you might think.

If you want to use it as a development platform for gesture interfaces you’ll want to install a Leap Motion in the specifically designed socket in the front, but otherwise, all you need to do is plug in an HDMI video source. That could be anything from a low-power wearable to a high-end gaming computer, depending on what your goals are.

[Graham] has not only provided the STLs for all the 3D printed parts and a bill of materials, but he’s also done a fantastic job of documenting the build process with a step-by-step guide. This isn’t some theoretical creation; you could order the parts right now and start building your very own Triton. If you’re looking for software, he’s also selling a Windows-based “Triton AR Launcher” for the princely sum of $4.99 that looks pretty slick, but it’s absolutely not required to use the hardware.

Of course, plenty of people are more than happy to stick with the traditional keyboard and monitor setup. It’s hard to say if wearable displays and gesture interfaces will really become the norm, of they’re better left to science fiction. But either way, we’re happy to see affordable open source platforms for experimenting with this cutting edge technology. On the off chance any of them become the standard in the coming decades, we’d hate to be stuck in some inescapable walled garden because nobody developed any open alternatives.

Should Have Used A Vacuum Tube 555

“You should have used a 555” has become a bit of a meme around these parts lately, and for good reason. There seems to be little that these ubiquitous chips can’t be used for, and in a world where code often substitutes for hardware, it’s easy to point to instances where one could have just used a simple timer chip instead.

Definitely not in the meme category, though, is this overkill vacuum tube 555 timer. It comes to us via [David Lovett], aka [Usagi Electric], who has lately caught the “hollow state” electronics bug and has been experimenting with all sorts of vacuum tube recreations of circuits we’re far more used to seeing rendered in silicon than glass. The urge to replicate the venerable 555 in nothing but vacuum tubes is understandable, as it uses little more than a pair of comparators and a flip-flop, circuits [David] has already built vacuum tube versions of. The only part left was the discharge transistor; a pentode was enlisted to stand in for that vital function, making the circuit complete.

To physically implement the design, [David] built a large PCB to hold the 18 vacuum tubes and the handful of resistors and capacitors needed. Mounted on eight outsized leads made from sheet steel, the circuit pays homage to the original 8-pin DIP form of the 555. The video below shows the design and build process as well as testing of all the common modes of operation for the timer chip.

You can check out more of our coverage of [David]’s vacuum tube adventures, which started with his reverse-engineering of an old IBM logic module. And while he did a great job explaining the inner workings of the 555, you might want to take a deeper dive into how the venerable chip came to be.

Continue reading “Should Have Used A Vacuum Tube 555”

Hackaday Links Column Banner

Hackaday Links: March 28, 2021

If you thought the global shortage of computer chips couldn’t get any worse, apparently you weren’t counting on 2021 looking back at 2020 and saying, “Hold my beer.” As if an impacted world waterway and fab fires weren’t enough to squeeze supply chains, now we learn that water restrictions could potentially impact chip production in Taiwan. The subtropical island usually counts on three or four typhoons a year to replenish its reservoirs, but 2020 saw no major typhoons in the region. This has plunged Taiwan into its worst drought since the mid-1960s, with water-use restrictions being enacted. These include a 15% reduction of supply to industrial users as well as shutting off the water entirely to non-industrial users for up to two days a week. So far, the restrictions haven’t directly impacted chip and display manufacturers, mostly because their fabs are located outside the drought zone. But for an industry where a single fab can use millions of gallons of water a day, it’s clearly time to start considering what happens if the drought worsens.

Speaking of the confluence of climate and technology, everyone problem remembers the disastrous Texas cold snap from last month, especially those who had to endure the wrath of the unusually brutal conditions in person. One such victim of the storm is Grady, everyone’s favorite YouTube civil engineer, who recently released a very good post-mortem on the engineering causes for the massive blackouts experienced after the cold snap. In the immediate aftermath of the event, we found it difficult to get anything approaching in-depth coverage on its engineering aspects — our coverage excepted, naturally — as so much of what we found was laden with political baggage. Grady does a commendable job of sticking to the facts as he goes over the engineering roots of the disaster and unpacks all the complexity of the infrastructure failures we witnessed. We really enjoyed his insights, and we wish him and all our friends in Texas the best of luck as they recover.

If you’re into the demoscene, chances are pretty good that you already know about the upcoming Revision 2021, the year’s big demoscene party. Like last year’s Revision, this will be a virtual gathering, but it seems like we’re all getting pretty used to that by now. The event is next weekend, so if you’ve got a cool demo, head over and register. Virtual or not, the bar was set pretty high last year, so there should be some interesting demos that come out of this year’s party.

Many of us suffer from the “good enough, move on” mode of project management, leaving our benches littered with breadboarded circuits that got far enough along to bore the hell out of us make a minimally useful contribution to the overall build. That’s why we love it when we get the chance to follow up on a build that has broken from that mode and progressed past the point where it originally caught our attention. A great example is Frank Olsen’s all-wood ribbon microphone. Of course, with magnets and an aluminum foil ribbon element needed, it wasn’t 100% wood, but it still was an interesting build when we first spied it, if a bit incomplete looking. Frank has fixed that in grand style by continuing the wood-construction theme that completes this all-wood replica of the iconic RCA Model 44 microphone. It looks fabulous and sounds fantastic; we can’t help but wonder how many times Frank glued his fingers together with all that CA adhesive, though.

Continue reading “Hackaday Links: March 28, 2021”

Code Talkers: Programming With Voice

IEEE Spectrum had an interesting post covering several companies trying to sell voice programming interfaces. Not programming APIs for speech recognition, but the replacement of the traditional text editor to produce programs.

The companies, Serenade and Talon, have very different styles. Serenade has fairly normal-sounding language, whereas Talon has you use very specific phrases and can even use eye tracking to figure out what you are looking at when you issue a command. There’s also mention of two open-source products (Aenae and Caster) that require you to use a third-party speech engine.

For an example of Talon’s input, imagine you want this line of code in your program:

name=extract_word(m)

You’d say this out loud: “Phrase name op equals snake extract word paren mad.” Not exactly how Star Trek envisioned voice programming.

For accessibility, this might be workable. It is hard for us to imagine a room full of developers all talking to make their computers enter C or Python code. Until we can say, “Computer, build a graphic using the data in file hackaday-27,” we think this is not going to go mainstream.

The actual speech recognition part is pretty much a commodity now. Making a reasonable set of guesses about what people will say and what they mean by it is something else. It seems like this works best when you have a very specific and limited vocabulary, like operating a 3D printer.