Using A Framework Mainboard For A Custom Gaming Handheld

The nearly final prototype case for the handheld Framework-based gaming system. (Credit: TommyB, YouTube)
The nearly final prototype case for the handheld Framework-based gaming system. (Credit: TommyB, YouTube)

Building your own handheld gaming console has been a popular project for many years, but recently it has become significantly easier to get a lot of power into a small package. Like many others, [TommyB] made his own Raspberry Pi SBC-based handheld in the past, which results in a rather bulky and underpowered package. A more performant solution would be to stuff laptop guts into a handheld case, but until Framework came onto the scene this wasn’t easy and would get you a sloppy one-off solution. With [TommyB]’s current handheld project he uses a standard Framework laptop mainboard, along with the official battery to get a very capable gaming system.

Getting the ergonomics and fit for the components just right took many tries, but eventually a prototype shell was designed that fits the Framework mainboard, the battery, twin Framework speakers, an 8″ LCD panel from Waveshare (connected via USB-C to HDMI) and mechanical switches for the buttons. These switches connect to an RP2040-based board that runs the GP2040-CE firmware, allowing the operating system to detect it as an XBox controller. Although still far from finished, it shows just how beneficial standard laptop parts are, with a massive gap in the market where Framework could make its own handheld shell available. We’re looking forward to [TommyB] demonstrating the finished version of his Framework handheld, and the inevitable upgrade from the 11th-gen Intel mainboard to one of the sparkling new mainboards with even better specs.

Thanks to [Keith Olson] for the tip.

Continue reading “Using A Framework Mainboard For A Custom Gaming Handheld”

Artist rendition of the Chandra telescope system in deep space. (Credit: NASA / James Vaughn)

The Chandra X-Ray Observatory Faces Shutdown In FY2025 Budget

The Chandra X-ray Observatory started its mission back in 1999 when Space Shuttle Columbia released it from its payload bay. Originally, it was supposed to serve only a five-year mission, but it has managed twenty-four years so far and counting, providing invaluable science along with the other Great Observatory: the Hubble Space Telescope. Unfortunately, NASA’s FY2025 budget now looks to threaten all space telescopes and Chandra in particular. This comes as part of the larger FY2025 US budget, which sees total funding for NASA increase by 2%, but not enough to prevent cuts in NASA’s space telescope operations.

NASA already anticipated this cut in 2023, with funding shifting to the Nancy Grace Roman Space Telescope (infrared spectrum, scheduled for 2027). Since Hubble is a joint operation with ESA, any shortfalls might be caught this way, but Chandra’s budget will go from 68.3M USD in FY2023 to 41.4M USD in FY2025 and from there plummeting to 5.2M USD by FY2029, effectively winding down the project and ending NASA’s flagship X-ray astronomy mission. This doesn’t sit well with everyone, with a website called Save Chandra now launched to petition the US government to save the observatory, noting that it still has a decade of fuel for its thrusters remaining and it also has stable mission costs.

Continue reading “The Chandra X-Ray Observatory Faces Shutdown In FY2025 Budget”

A Fully Automatic British Breakfast: Ready While You Sleep

What do you mean, the temporary breadboard setup went into production? (Credit: Gregulations, YouTube)
What do you mean, the temporary breadboard setup went into production? (Credit: [Gregulations], YouTube)
Among all the amazing technologies that were promised to us, there is one that is much more egregious than the lack of flying cars and real hovering hoverboards: the lack of fully automated breakfast-maker machines. Instead we find ourselves handling the same dumb appliances each morning as we make a healthy breakfast that we then have time to wolf down before rushing out of the door to still be a few minutes late for work. When [Greg] researched machines that could automatically prepare breakfast, he came up empty, which led him down the rabbit hole of the Autochef-9000.

Although often featured in movies – ranging from Back to the Future to Wallace and Gromit – the contraptions in those are rarely practical, and real-life attempts often suffer the problem of feature creep as they have to handle too many ingredients and operations. This is where [Greg] found redemption in the simplicity of a proper British breakfast: beans, toast, sausages (sossys), and eggs. Months of CAD, welding, breadboarding, and writing Arduino code later, he made a machine that can open a can of beans, toast bread, boil eggs, fry up sausages, and deposit it all on a plate, all ready for that morning breakfast first thing when you stroll into the kitchen.

Thanks to [htky] for the tip.

Continue reading “A Fully Automatic British Breakfast: Ready While You Sleep”

NASA Engineers Poke Voyager 1 And Receive Memory Dump

For months, there has been a rising fear that we may have to say farewell to the Voyager 1 spacecraft after it began to send back garbled data. Now, in a sudden twist, Voyager 1 sent back a read-out of the Flight Data Subsystem (FDS) memory after a “poke” command, which both gives some hope that the spacecraft is in a better condition than feared while also allows engineers to dig through the returned memory read-out for clues. Although this data was not sent in the format that the FDS is supposed to use when it’s working correctly, it’s nevertheless readable.

It was previously suspected that the issue lay with the telemetry modulation unit (TMU), but has since been nailed down to the FDS itself.  This comes after NASA engineers have been updating the firmware on both spacecraft to extend their lifespan, but it’s too early to consider this as a possible reason. Now, as a result of the “poke” instruction – which commands the computer to try different sequences in its firmware in case part of it has been corrupted – engineers can compare it to previous downloads to hopefully figure out the cause behind the FDS problems and a possible solution.

Inspired by this news of the decoded memory download, Nadia Drake – daughter of Frank Drake – wrote about how it affects not only the engineers who have worked on the Voyager mission for the past decades but also her own thoughts about the two Voyager spacecraft. Not only do they form a lasting reminder of her father and so many of his colleagues, but the silence that would follow if we can no longer communicate with these spacecraft would be profound. Still, this new hope is better than the earlier news about this plucky little spaceship.

Thanks to [Mark Stevens] for the tip.

Making Floating Point Calculations Less Cursed When Accuracy Matters

Inverting the earlier exponentiation to reduce floating point arithmetic error. (Credit: exozy)
Inverting the earlier exponentiation to reduce floating point arithmetic error. (Credit: exozy)

An unfortunate reality of trying to represent continuous real numbers in a fixed space (e.g. with a limited number of bits) is that this comes with an inevitable loss of both precision and accuracy. Although floating point arithmetic standards – like the commonly used IEEE 754 – seek to minimize this error, it’s inevitable that across the range of a floating point variable loss of precision occurs. This is what [exozy] demonstrates, by showing just how big the error can get when performing a simple division of the exponential of an input value by the original value. This results in an amazing error of over 10%, which leads to the question of how to best fix this.

Obviously, if you have the option, you can simply increase the precision of the floating point variable, from 32-bit to 64- or even 256-bit, but this only gets you so far. The solution which [exozy] shows here involves using redundant computation by inverting the result of ex. In a demonstration using Python code (which uses IEEE 754 double precision internally), this almost eradicates the error. Other than proving that floating point arithmetic is cursed, this also raises the question of why this works.

Continue reading “Making Floating Point Calculations Less Cursed When Accuracy Matters”

Two ICL PERQ 1 workstation computers, Department of Computer Science, North Machine Hall, James Clerk Maxwell Building, University of Edinburgh. (Credit: J. Gordon Hughes)

The Flex Computer System: UK’s Forgotten Capability Computer Architecture

During the 1970s many different computer architectures were being developed, many of them focused on making computer systems easier and more effective to use. The Flex Machine developed at the UK Ministry of Defence’s Royal Signals and Radar Establishment (RSRE) was one of them, falling in the category of Capability Architectures. These architectures required hardware with programmable microcode, which required either custom hardware, or computer systems like the Xerox Alto-inspired ICL PERQ (pictured). What’s interesting about Flex is that it didn’t just remain in the 1980s as a quaint footnote, but as detailed by [Martin C. Atkins] – who worked on the system – evolved into the Ten15 system, which later got renamed to TenDRA.

Capability architectures have a long history – including the Intel iAPX 432 and more recent implementations – but they all have in common is that they effectively implement an object-based memory architecture, rather than the low-level, flat memory space that we usually see with computer systems. These object-based capabilities, as they were termed, provides a level of memory protection and security that would be hard to implement otherwise. The book Capability-Based Computer Systems by [Henry M. Levy] forms a good introduction here.

Continue reading “The Flex Computer System: UK’s Forgotten Capability Computer Architecture”

Gentle Introduction To White Light Interferometry

Screenshot of the Zygo white light interferometry microscope software. (Credit: Huygens Optics)
Screenshot of the Zygo white light interferometry microscope software. (Credit: Huygens Optics)

White light interferometry (WLI) is a contact-free optical method for measuring surface height. It uses the phase difference between the light reflected off a reference mirror and the target sample to calculate the height profile of the sample’s surface. As complex as this sounds, it doesn’t take expensive hardware to build a WLI microscope, as [Huygen Optics] explains in a detailed introductory video on the topic. At its core you need a source of white light (e.g. a white LED), with a way to focus the light so as to get a spatially coherent light source, like aluminium foil with a pin hole and a lens.

This light source then targets a beam splitter, which splits the light into one beam that targets the sample, and one that targets the reference mirror. When both beams are reflected and return to the beam splitter, part of the reflected light from either side ends up at the camera, which captures the result of the reference and sample beams after their interference (i.e. combination of the amplitudes). This creates a Michelson interferometer, which is simple, but quite low resolution. For the demonstrated Zygo Newview 100 WLI microscope this is the first objective used, followed by a more recent innovation: the Mirau interferometer, which integrates the reference mirror in such a manner that much higher resolutions are possible, down to a few µm.

Continue reading “Gentle Introduction To White Light Interferometry”