X-Ray Investigations Hack Chat

Join us on Wednesday, January 24 at noon Pacific for the X-Ray Investigation Hack Chat with Ahron Wayne!

It’s hard to imagine a world where we didn’t figure out how to use X-rays to peer inside things. Before Röntgen’s discovery that X-rays could penetrate living tissue, doctors had only limited (and often unpleasant) ways to get a look at what was going on inside the human body, and few of us would want to return to those days.

As fantastically useful as X-rays and later computed tomography (CT) became in medicine, it didn’t take too long for other uses for the technology to come along. Non-clinical applications for X-ray and CT abound, including their use in non-invasively exploring relics of immense archaeological value. One recent effort in this space that gained a lot of coverage in the press was the combination of CT imaging and machine learning to read the ink inside carbonized papyrus scrolls from the ruins of Pompeii.

join-hack-chatThe result was the “Vesuvius Challenge,” where different teams looked for techniques to virtually unwrap the roasted relics. Ahron’s contribution to the project was a little unusual — he bought a used desktop CT scanner, fixed it up, and started experimenting with reading ink from the carbonized remains of simulated papyrus scrolls. In other words, he made some scrolls, cooked them to beyond well-done in the oven, and tried to understand what happens to ink on papyrus that gets blasted by a volcano. If that’s not enough to get you to stop by the Hack Chat when Ahron joins us, we’re not sure what else would be! Suffice it to say we’re pretty excited about what Ahron has to say about DIY CT,  X-rays, collaborative open-source citizen science, and unwrapping the mysteries of Pompeii.

Our Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, January 24 at 12:00 PM Pacific time. If time zones have you tied up, we have a handy time zone converter.

Featured image: Daderot, CC0, via Wikimedia Commons

Fixing A PDP-11/03 Power Supply Is Easy When You Understand It

After we last saw [David Lovett] of [Usagi Electric], he was knee-deep in trying to fix a DEC PDP-11/03 power supply, which fortunately led to a fixed PSU and a very happy PDP-11/23 system installed in the enclosure, as he covers in today’s video. Previously, we had covered his debugging attempt of this very much dead power supply, which had led [David] down many fruitless rabbitholes. By the time he was taking various components off the board to try and induce certain results, he threw in the towel and went back to the drawing board, assisted with many community comments.

The 5V rail on a DEC PDP-11/03 power supply. (Credit: David Lovett)
The 5V rail on a DEC PDP-11/03 power supply. (Credit: David Lovett)

Much of the confusion came down to not really understanding how this PDP-11/03 PSU design works, which isn’t that crazy in hindsight, considering how quaint it is. Although [David] originally focused on the +5V rail, a small detail that was in the schematics is that the 5V rail is based around a 7805 that has its ground referenced to the -15V rail.

It is this 7805 that provides a linearly regulated 5V rail up till its current limit, at which point the control transistor gets biased sufficiently to start conducting, which eventually triggers the driver transistor that is responsible for driving the pass switch transistor. This then charges L2 from the unregulated supply, which is used effectively as a switching mode power supply until the current across the 7805 drops sufficiently that it becomes the primary 5V rail source again. This repeats at a kHz rate, making it more or less an SMPS as we know it today, but heavily reliant on the -15V rail as can be observed in the schematic. Continue reading “Fixing A PDP-11/03 Power Supply Is Easy When You Understand It”

Bell Labs Is Leaving The Building

If you ever had the occasion to visit Bell Labs at Murray Hill, New Jersey, or any of the nearby satellite sites, but you didn’t work there, you were probably envious. For one thing, some of the most brilliant people in the world worked there. Plus, there is the weight of history — Bell Labs had a hand in ten Nobel prizes, five Turing awards, 22 IEEE Medals of Honor, and over 20,000 patents, including several that have literally changed the world. They developed, among other things, the transistor, Unix, and a host of other high-tech inventions. Of course, Bell Labs hasn’t been Bell for a while — Nokia now owns it. And Nokia has plans to move the headquarters lab from its historic Murray Hill campus to nearby New Brunswick. (That’s New Jersey, not Canada.)

If your friends aren’t impressed by Nobels, it is worth mentioning the lab has also won five Emmy awards, a Grammy, and an Academy award. Not bad for a bunch of engineers and scientists. Nokia bought Alcatel-Lucent, who had wound up with Bell Labs after the phone company was split up and AT&T spun off Lucent.

Continue reading “Bell Labs Is Leaving The Building”

3D Printed Screw Compressor Revisited

[Indeterminate Design] tried to 3D print a screw compressor some time ago but wasn’t satisfied with the result. He’s trying it again, and you can check it out in the video below. You can also download the 3D printable files.

This isn’t a 3D-printed keychain. The screw threads have to mesh with a small space between them, and the design is not trivial. Even if you don’t want to build your own, the look inside the engineering behind these devices is interesting, and there is quite a bit of background about how the rotor’s shapes are optimized.

Continue reading “3D Printed Screw Compressor Revisited”

Haier Europe Eases Off On Legal Threat And Seeks Dialogue

After initially sending a cease and desist order to [Andre Basche] – the developer of a Haier hOn plugin for Home Assistant – Haier Europe’s head of Brand and IoT has now penned a much more amicable response, seeking to enter into dialogue in search of a solution for both parties.

This latest development is detailed both in the ongoing GitHub issue, as well as the Takedown FAQ and Timeline document that [Andre] created to keep track of everything that’s going on since we last checked in on the situation. As things stand, there is hope that Haier Europe may relent, especially as the company’s US division has shown no inclinations to join in on the original C&D.

In the confusion following the initial C&D announcement demanding the take-down of [Andre]’s hOn-related repositories, it was not clear to many which Haier was involved. As it turns out, Haier Europe as a separately legal entity apparently decided to go on this course alone, with Haier US distancing themselves from the issue. In that same Reddit thread it’s noted that GE Appliances (part of Haier US) has had a local API available for years. This makes Haier Europe the odd one out, even as they’re attempting some damage control now.

Amidst this whirlwind of developments, we hope that Haier Europe can indeed reach an amicable solution with the community, whether it’s continued API usage, or the development of a local API.

FM Radio Is Discriminating

AM radios were easy to understand. The strength of the signal goes up and down, and the audio follows. FM radio is a little more difficult. [AllAmericanFiveRadio] has an old tube FM set and takes us on a tour of how the FM discriminator works. You can see the video below.

The first step is to look at the IF signal on the scope. It is hard to see, but the frequency is changing, and that’s the basis of modulation that the discriminator has to resolve.

Continue reading “FM Radio Is Discriminating”

640k Was Never Enough For Anyone: How DOS Broke Free

On modern desktop and laptop computers, there is rarely a need to think about memory. We all have many gigabytes of the stuff, and it’s just there. Our operating system does the heavy lifting of working out what goes where and what needs to be paged to disk, and we just get on with reading Hackaday, that noblest of computing pursuits. This was not always the case though, and for early PCs in particular the limitations of the 8086 processor gave the need for some significant gymnastics in search of an extra few kilobytes. [Julio Merion] has an interesting run-down of the DOS memory map, and how memory expansion happened on computers physically unable to see much of it.

The 8086 has a 20-bit address bus, giving it access to a maximum of 1 megabyte. When IBM made the PC they needed space for the BIOS, the display, and the various accessory ROMs intended to come with expansion cards. Thus they allocated a maximum 640k of the map for RAM, and many early machines shipped with much less than that. The quote from Bill Gates about 640k being enough for anyone is probably apocryphal, but it was pretty clear as the 1980s wore on that more would be needed. The post goes into how memory expansion worked, with a 64k page mapped to switchable RAM on a card, and touches on how DOS managed extended memory above 1 Mb on the later processors that supported it. We dimly remember there also being a device driver that would map the unused graphics memory as EMS when the graphics card was running in text mode, but such horrors are best left behind.

Of course, some of the tricks to boost RAM were nothing but snake oil.

8086 header: Thomas Nguyen, CC BY-SA 4.0