The Life Cycle Of Nuclear Fission Fuel: From Stars To Burn-Up

Outdone only by nuclear fusion, the process of nuclear fission releases enormous amounts of energy. The ‘spicy rocks’ that are at the core of both natural and artificial fission reactors are generally composed of uranium-235 (U-235) along with other isotopes that may or may not play a role in the fission process. A very long time ago when the Earth was still very young, the ratio of fissile U-235 to fertile U-238 was sufficiently high that nuclear fission would spontaneously commence, as happened at what is now the Oklo region of Gabon.

Although natural decay of U-235 means that this is unlikely to happen again, we humans have learned to take uranium ore and start a controlled fission process in reactors, beginning in the 1940s. This can be done using natural uranium ore, or with enriched (i.e. higher U-235 levels) uranium. In a standard light-water reactor (LWR) a few percent of U-235 is used up this way, after which fission products, mostly minor actinides, begin to inhibit the fission process, and fresh fuel is inserted.

This spent fuel can then have these contaminants removed to create fresh fuel through reprocessing, but this is only one of the ways we have to extract most of the energy from uranium, thorium, and other actinides like plutonium. Although actinides like uranium and thorium are among the most abundant elements in the Earth’s crust and oceans, there are good reasons to not simply dig up fresh ore to refuel reactors with.

Continue reading “The Life Cycle Of Nuclear Fission Fuel: From Stars To Burn-Up”

FLOSS Weekly Episode 809: Pi4J – Stable And Boring On The Raspberry Pi

This week, Jonathan Bennett and David Ruggles chat with Frank Delporte about Pi4J, the friendly Java libraries for the Raspberry Pi, that expose GPIO, SPI, I2C and other IO interfaces. Why would anyone want to use Java for the Pi? And what’s changed since the project started? Listen to find out!

Continue reading “FLOSS Weekly Episode 809: Pi4J – Stable And Boring On The Raspberry Pi”

Making Sense Of Real-Time Operating Systems In 2024

The best part about real-time OS (RTOS) availability in 2024 is that we developers are positively spoiled for choice, but as a corollary this also makes it a complete pain to determine what the optimal choice for a project is. Beyond simply opting for a safe choice like FreeRTOS for an MCU project and figuring out any implications later during the development process, it can pay off massively to invest some time up-front matching the project requirements with the features offered by these various RTOSes. A few years ago I wrote a primer on the various levels of ‘real-time’ and whether you may even just want to forego an RTOS at all and use a simple Big Loop™ & interrupt-based design.

With such design parameters in mind, we can then look more clearly at the available RTOS options available today, which is the focus of this article. Obviously it won’t be an exhaustive comparison, and especially projects like FreeRTOS have seen themselves customized to various degrees by manufacturers like ST Microelectronics and Espressif, among others. This also brings to the forefront less pleasant considerations, such as expected support levels, as illustrated by e.g. Microsoft’s Azure RTOS (formerly ThreadX) recently getting moved to the Eclipse Foundation as the Eclipse ThreadX open source project. On one hand this could make it a solid open-source licensed RTOS, or it could have been open sourced because Microsoft has moved on to something else and cleared out its cupboard.

Thus without further ado, let’s have a look at RTOSes in 2024 and which ones are worth considering, in my opinion.

Continue reading “Making Sense Of Real-Time Operating Systems In 2024”

A Teletype By Any Other Name: The Early E-mail And Wordprocessor

Some brand names become the de facto name for the generic product. Xerox, for example. Or Velcro. Teletype was a trademark, but it has come to mean just about any teleprinter communicating with another teleprinter or a computer. The actual trademark belonged to The Teletype Corporation, part of Western Electric, which was, of course, part of AT&T. But there were many other companies that made teleprinters, some of which were very influential.

The teleprinter predates the computer by quite a bit. The original impetus for their development was to reduce the need for skilled telegraph operators. In addition, they found use as crude wordprocessors, although that term wouldn’t be used for quite some time.

Continue reading “A Teletype By Any Other Name: The Early E-mail And Wordprocessor”

Retrotechtacular: Color TV

We have often wondered if people dreamed in black and white before the advent of photography. While color pictures eventually became the norm, black and white TV was common for many years. After all, a TV set was a big investment, so people didn’t run out and buy the latest TV every year. Even if you did buy a new or used TV, a black and white model was much less expensive and, for many years, some shows were in black and white anyway. RCA, of course, wanted you to buy a color set. [PeriscopeFilm] has a 1963 promotional film from RCA extolling the virtues of a color set. The video also shows something about how the sets were made, as you can see below.

We aren’t sure we’d have led with the idea that color could save your life in this context, but we have to salute the melodrama. There is a good bit of footage of picture tube manufacturing, although the technical detail is — understandably — aimed at the general public.

Continue reading “Retrotechtacular: Color TV”

Ubiquitous Successful Bus: Version 3

USB 2 is the USB we all know and love. But about ten years ago, USB got an upgrade: USB 3.0. And it’s a lot faster. It started off ten times the speed of USB 2, with 5 Gbps, and later got 20 Gbps and 40 Gbps revisions. How does that work, and how do you hack on it? Well, for a start, it’s very different from USB 2, and the hacking differs in many important ways.

In fact, USB 3 is an entirely separate interface from USB 2, and it does not depend on USB 2 in any way whatsoever – some people think that USB 3 negotiation happens through USB 2, but that’s a complete myth. USB 2 and USB 3 are electrically, physically, and logically distinct interfaces. Except for the fact that USB 3 is backwards compatible with USB 2, they are simply entirely different.

This also means that every USB-A port with USB 3 capabilities (typically blue, but not always) carries two interfaces; indeed, if you want, you can split a typical USB 3 port into a USB 3-only USB-A port and a USB 2-only USB-A port. USB 3-only ports are not legal per USB 3 standard, you’re expected to keep USB 2 there, but only for user convenience; you can split it with a hub and get, like, three extra USB 2 branches for your own use. Even if it’s forbidden, it works flawlessly – it’s what I’m currently using to connect my mouse to my laptop as I’m typing this!

Not to say that USB 3 is all easy to work with – there’s a fair bit of complexity.

Continue reading “Ubiquitous Successful Bus: Version 3”

The Badge Hacks Of Supercon

We just got home from Supercon and well, it was super. It was great to see everyone, and meet a whole bunch of new folks to boot! The talks were great, and you can see a good half of them already on the Hackaday YouTube channel, so for that you didn’t even have to be there.

The badge hacks were, as with most years, out of this world. I’ll admit that my cheeks were sore from laughing so much after emceeing it this year, due in no small part to two hilarious AI projects, both of which were also righteous hacks in addition to full-on comedy routines. A group of six programmers got all of their hacks working together, and the I2C-to-MQTT bridge had badges blinking in sync even in the audience. You want blinkies? We had blinkies.

But the hack that warmed everyones’ hearts was “I figured it out” by [Connie]. Before this weekend, she had never coded MicroPython and didn’t know anything about I2C. But yet by Sunday afternoon, she made a sweet spiral animation on the LED wheel, and blinked the RGBs in the touchwheel.

What I love about the Hackaday audience is that, when the chips are down, someone doing something new for the first time is valued as much as some of the more showy work done by more experienced programmers. Hacking is also about learning and pushing out boundaries after all. The shouts for “I figured it out” were louder than any others in the graphics hacks category, it took home a prize, and I was smiling from ear to ear.

Hackaday can learn from this too. [Connie]’s hack definitely shows the need for another badge-hack category, first timers, because we absolutely should recognize first tries. There was also a strong petition / protest from people who had worked new hacks onto previous year’s badges – like [Andy] and [koppanyh]’s addition of bit-banged I2C to the Voja 4 badge from two years ago, and [Instant Arcade]’s Polar Pacman, which he named “Ineligible for this Competition” in protest. Touche.

We’re stoked to learn new things, see new hacks, and basically just catch up with everything folks did over the weekend. We can’t wait to see what you’re up to next year!