38C3: Save Your Satellite With These Three Simple Tricks

December 30, 2024 by 11 Comments

BEESAT-1 is a 1U cubesat launched in 2009 by the Technical University of Berlin. Like all good satellites, it has redundant computers onboard, so when the first one failed in 2011, it just switched over to the second. And when the backup failed in 2013, well, the satellite was “dead” — or rather sending back all zeroes. Until [PistonMiner] took a look at it, that is.

Getting the job done required debugging the firmware remotely — like 700 km remotely. Because it was sending back all zeroes, but sending back valid zeroes, that meant there was something wrong either in the data collection or the assembly of the telemetry frames. A quick experiment confirmed that the assembly routine fired off very infrequently, which was a parameter that’s modifiable in SRAM. Setting a shorter assembly time lead to success: valid telemetry frame.

Then comes the job of patching the bird in flight. [PistonMiner] pulled the flash down, and cobbled together a model of the satellite to practice with in the lab. And that’s when they discovered that the satellite doesn’t support software upload to flash, but does allow writing parameter words. The hack was an abuse of the fact that the original code was written in C++. Intercepting the vtables let them run their own commands without the flash read and write conflicting.

Of course, nothing is that easy. Bugs upon bugs, combined with the short communication window, made it even more challenging. And then there was the bizarre bit with the camera firing off after every flash dump because of a missing break in a case statement. But the camera never worked anyway, because the firmware didn’t get finished before launch.

Challenge accepted: [PistonMiner] got it working, and after fifteen years in space, and ten years of being “dead”, BEESAT-1 was taking photos again. What caused the initial problem? NAND flash memory needs to be cleared to zeroes before it’s written, and a bug in the code lead to a long pause between the two, during which a watchdog timeout fired and the satellite reset, blanking the flash.

This talk is absolutely fantastic, but may be of limited practical use unless you have a long-dormant satellite to play around with. We can nearly guarantee that after watching this talk, you will wish that you did. If so, the Orbital Index can help you get started.

Release Your Inner Ansel Adams With The Shitty Camera Challenge

December 30, 2024 by 22 Comments

Social media microblogging has brought us many annoying things, but some of the good things that have come to us through its seductive scrolling are those ad-hoc interest based communities which congregate around a hashtag. There’s one which has entranced me over the past few years which I’d like to share with you; the Shitty Camera Challenge. The premise is simple: take photographs with a shitty camera, and share them online. The promise meanwhile is to free photography from kit acquisition, and instead celebrate the cheap, the awful, the weird, and the wonderful in persuading these photographic nonentities to deliver beautiful pictures.

Where’s The Hack In Taking A Photo?

Of course, we can already hear you asking where the hack is in taking a photo. And you’d be right, because any fool can buy a disposable camera and press the shutter a few times. But from a hardware hacker perspective this exposes the true art of camera hacking, because not all shitty cameras can produce pictures without some work.

The #ShittyCameraChallenge has a list of cameras likely to be considered shitty enough, they include disposables, focus free cameras, instant cameras, and the cheap plastic cameras such as Lomo or Holga. But also on the list are models which use dead film formats, and less capable digital cameras. It’s a very subjective definition, and thus in our field everything from a Game Boy camera or a Raspberry Pi camera module to a home-made medium format camera could be considered shitty. Ans since even the ready-made shitty cameras are usually cheap and unloved second-hand, there’s a whole field of camera repair and hacking that opens up. Finally, here’s a photography competition that’s fairly and squarely on the bench of Hackaday readers. Continue reading “Release Your Inner Ansel Adams With The Shitty Camera Challenge” →

Illustrated Kristina with an IBM Model M keyboard floating between her hands.

Keebin’ With Kristina: The One With The Copycat Keyboard

December 30, 2024 by 1 Comment

This is Crater75, an almost completely from-scratch row-staggered wireless split board that [United_Parfait_6383] has been working on for a few months. Everything but the keycaps and switches is DIY.

The Crater75 split keyboard, which features OLEDs on the Function row.
Image by [United_Parfait_6383] via reddit
As cool as a keyboard full of screens might seem, can you imagine what it would be like to type at speed on a sea of slick surfaces? Not very nice, I’m thinking. But having them solely on the Function row seems like the perfect compromise. Here, the Function row keys interact with foreground applications, and change with whatever has focus. For the curious, those are 0.42″ OLEDs from Ali with a resolution of 72×40.

I’m not sure what’s going on internally, but the two sides connect with magnets, and either side’s USB-C can be used to charge the board. Both sides have a 2100 mAh Li-Po battery, and the average current of the OLED displays is low enough that the board can run for months on a single charge.

The switches are Gateron low-profiles and are wearing keycaps recycled from a Keychron, which add to the professional finish. Speaking of, the enclosures were manufactured by JLC3DP using the Nylon Multi-Jet Fusion process, but [United_Parfait_6383] says the left side feels too light, so the next revision will likely be CNC’d aluminium. Be sure to check out this short video of Crater75 in action.

Continue reading “Keebin’ With Kristina: The One With The Copycat Keyboard” →

Bringing OpenStreetMap Data Into Minecraft

December 30, 2024 by 11 Comments

Over the years, dedicated gamers have created incredible recreations of real (and not so real) locations and structures within the confines of Minecraft. Thanks to their efforts, you can explore everything from New York city to Middle Earth and the U.S.S. Enterprise in 1:1: scale.

But what if you wanted to recreate your own town, and didn’t have the hundreds of hours of spare time necessary to do it by hand? Enter Arnis, an open source project from [Louis Erbkamm] that can pull in geographic data from OpenStreetMap and turn it into a highly detailed Minecraft map with just a few keystrokes.

The tool, written in Rust, can be either run via an interactive graphical interface or on the command line. In either case, you provide Arnis with the latitude and longitude for a bounding box around whatever you want to import into the game. [Louis] warns that the resulting process is fairly computationally heavy, so you should start be experimenting with small areas.

Once generated, the map can be loaded into the Java Edition of Minecraft. This refers to the original build of the game that predates the Microsoft buyout. Once Redmond took over they spearheaded a new version of the game written in C++ which was then ported over to mobile operating systems and game consoles. Long story short, if you want to wander around a Minecraft version of your home town, you’ll have to do it on your desktop computer instead of your Nintendo Switch.

While the tool is usable in its current state, [Louis] has a fairly long list of features that either still need to be implemented or could use some improvements. From the number of pull requests that have been merged in, it looks like any assistance the community can provide to make Arnis as capable as possible is welcome, so feel free to lend a hand if you’ve got that geospatial fever.

We’ve seen several examples of hackers bringing objects from Minecraft into the physical world, so it’s refreshing to see a bit of our reality sneaking into the game’s blocky universe.

The Twisted History Of Ethernet On Twisted Pair Wiring

December 30, 2024 by 54 Comments

We all take Ethernet and its ubiquitous RJ-45 connector for granted these days. But Ethernet didn’t start with twisted pair cable. [Mark] and [Ben] at The Serial Port YouTube channel are taking a deep dive into the twisted history of Ethernet on twisted pair wiring. The earliest forms of Ethernet used RG-8 style coaxial cable. It’s a thick, stiff cable requiring special vampire taps and lots of expensive equipment to operate.

The industry added BNC connectors and RG-58 coax for “cheapernet” or 10Base2. This reduced cost, but still had some issues. Anyone who worked in an office wired with 10Base2 can attest to the network drops whenever a cable was kicked out or a terminator was dropped.

The spark came when [Tim Rock] of AT&T realized that the telephone cables already installed in offices around the world could be used for network traffic. [Tim] and a team of engineers from five different companies pitched their idea to the IEEE 802.3 committee on Feb 14, 1984.

The idea wasn’t popular though — Companies like 3COM, and Digital Equipment Corporation had issues with the network topology and the wiring itself. It took ten years of work and a Herculean effort by IEEE committee chairwoman [Pat Thaler] to create the standard the world eventually came to know as 10Base-T. These days we’re running 10 Gigabit Ethernet over those same connectors.

For those who don’t know, this video is part of a much larger series about Ethernet, covering both history and practical applications. We also covered the 40th anniversary of Ethernet in 2020.

Continue reading “The Twisted History Of Ethernet On Twisted Pair Wiring” →

Ball Nut Modification Charts A Middle Course Between Building And Buying

December 29, 2024 by 7 Comments

A lot of the projects we feature here on Hackaday engender the classic “build versus buy” argument. We’ve always been puzzled by that; if anyone can appreciate the sheer joy of making something rather than buying it, it should be our readers. But there’s something to be said for buying the stuff you can buy and concentrating your effort on the bespoke aspects of the project. It’s perhaps not as exciting, but needs must, oftentimes.

Let’s not forget there’s a third way though, which [Andy] explores with this ball nut modification project. Keen-eyed readers will recall [Andy]’s recent scratch-built ball screw build, in service of some top-secret, hush-hush project related to world domination and total subjugation of humanity. His homebrew efforts in this regard were a great lesson in how to machine a complex mechanism to work in a constrained space. Still, it left folks wondering why he’d go to all the trouble when he could have just trimmed an off-the-shelf part down to size. So, he decided to give that a try.

Continue reading “Ball Nut Modification Charts A Middle Course Between Building And Buying” →

[Kerry Wong] Talks (and Talks) About A 300 MHz Oscilloscope

December 29, 2024 by 10 Comments

There aren’t many people who could do an hour-long video reviewing an oscilloscope, but [Kerry Wong] is definitely one of them. This time, he’s looking at a UNI-T MSO2304X 300 MHz scope. The review might be a little long, but the scope — like many modern scopes — has a lot of features for measuring power, accommodating digital signals with an add-on pod, and protocol decoding.

The scope has a touchscreen and four normal inputs, plus two frequency generator outputs. You can also use a mouse or an external display. But, of course, what you really want to know is how the scope performs when reading signals.

Continue reading “[Kerry Wong] Talks (and Talks) About A 300 MHz Oscilloscope” →