The video starts with a high-level overview of the schematic, which as you might have guessed, essentially puts two identical floppy controllers on the same board. You can tell this design was put together during the current chip shortage, as [Sergey] was careful to include some wiggle room if certain parts became unavailable and had to be swapped out for the alternatives listed in the BOM. It’s a decision that already paid off for [Gadget Reboot], as in some cases he had to go with the second-choice ICs.
[Gadget Reboot] was in for something of a surprise when he submitted the board for fabrication, as selecting the option for gold contacts on the edge connector made the production cost jump from $5 to nearly $300. He details how he was able to bring that cost back down a bit, but it still ended up being more than 10 times as expensive as the base price.
The second half of the video is dedicated to configuring the Monster FDC, which will certainly be a helpful resource for anyone looking to put this board to work in their own system. [Gadget Reboot] demonstrates using the board with “only” four floppy drives, and everything looks to work quite well.
When it comes to an engineering marvel like the James Webb Space Telescope, the technology involved is so specialized that there’s precious little the average person can truly relate to. We’re talking about an infrared observatory that cost $10 billion to build and operates at a temperature of 50 K (−223 °C; −370 °F), 1.5 million kilometers (930,000 mi) from Earth — you wouldn’t exactly expect it to share any parts with your run-of-the-mill laptop.
But it would be a lot easier for the public to understand if it did. So it’s really no surprise that this week we saw several tech sites running headlines about the “tiny solid state drive” inside the James Webb Space Telescope. They marveled at the observatory’s ability to deliver such incredible images with only 68 gigabytes of onboard storage, a figure below what you’d expect to see on a mid-tier smartphone these days. Focusing on the solid state drive (SSD) and its relatively meager capacity gave these articles a touchstone that was easy to grasp by a mainstream audience. Even if it was a flawed comparison, readers came away with a fun fact for the water cooler — “My computer’s got a bigger drive than the James Webb.”
Of course, we know that NASA didn’t hit up eBay for an outdated Samsung EVO SSD to slap into their next-generation space observatory. The reality is that the solid state drive, known officially as the Solid State Recorder (SSR), was custom built to meet the exact requirements of the JWST’s mission; just like every other component on the spacecraft. Likewise, its somewhat unusual 68 GB capacity isn’t just some arbitrary number, it was precisely calculated given the needs of the scientific instruments onboard.
With so much buzz about the James Webb Space Telescope’s storage capacity, or lack thereof, in the news, it seemed like an excellent time to dive a bit deeper into this particular subsystem of the observatory. How is the SSR utilized, how did engineers land on that specific capacity, and how does its design compare to previous space telescopes such as the Hubble?
Hackaday Editor-in-Chief Elliot Williams and Managing Editor Tom Nardi start this week’s podcast off with an announcement the community has been waiting years for: the return of the Hackaday Supercon! While there’s still some logistical details to hammer out, we’re all extremely excited to return to a live con and can’t wait to share more as we get closer to November. Of course you can’t have Supercon without the Hackaday Prize, which just so happens to be wrapping up its Hack it Back challenge this weekend.
In other news, we’ll talk about the developing situation regarding the GPLv3 firmware running on Ortur’s laser engravers (don’t worry, it’s good news for a change), and a particularly impressive fix that kept a high-end industrial 3D printer out of the scrapheap. We’ll also fawn over a pair of fantastically documented projects, learn about the fascinating origins of the lowly fire hydrant, and speculate wildly about the tidal wave of dead solar panels looming menacingly in the distance.
While the 2022 Hackaday Prize as a whole winds its way through a good chunk of the year, each individual challenge that makes up the competition only sticks around for a limited time. As hard as it might be to believe, our time with theHack it Back challenge is nearly at a close, with just a few days left to enter your project before the July 24th deadline.
Each challenge in this year’s Hackaday Prize has been designed around the core themes of sustainability, resiliency, and circularity — and for the Hack it Back phase of the competition we asked hackers to essentially keep as much hardware out of the landfill as possible. That could mean making a simple fix that puts a piece of equipment back into service, or it might be a be complete rebuild of an older device to bring it up to modern standards. These are the kind of projects Hackaday was built on, so turning it into an official challenge this year made perfect sense. Continue reading “Don’t Miss Your Last Chance To Enter The Hack It Back Challenge”→
There was a time, not so long ago, when folks who wanted to make their own custom PCBs would have found themselves in the market for a bucket of acid and a second-hand laser printer. These days, all you have to do is click a few buttons in your EDA program of choice and send the files off for fabrication. It’s easy, cheap, and nobody ends up with chemical burns.
This has obviously had a transformative effect on the electronics hobby — when you can place traces on a PCB like an artist using a brush, it’s only a matter of time before you get projects like [Logan Arkema]’s DCTransistor. This open source board uses carefully arranged RGB LEDs to recreate the Washington Metropolitan Area Transit Authority (WMATA) metro map, and thanks to an ESP8266 connected to their API, can display the positions of trains in real-time.
If you’re getting a sense of déjà vu here, it’s not just in your head. We’ve seen similar maps created for other major metropolitan areas, and [Logan] certainly isn’t trying to take credit for the idea. In fact, he was a bit surprised to find that nobody had ever made one for the DC area — so he decided to take on the challenge himself. He reasoned it would be a good way to hone his PCB design skills and become more comfortable with embedded development. We’d say the end result proves his theory correct, and makes one more city that can boast about its IoT cartography.
Looking to hang a DCTransistor on your own wall? [Logan] says he’ll be dropping the board design files and schematics into the project’s GitHub repository soon, and he also plans on selling pre-made boards in the near future.
The average person’s perception of a ham radio operator, assuming they even know what that means, is more than likely some graybeard huddled over the knobs of a war-surplus transmitter in the wee small hours of the morning. It’s a mental image that, admittedly, isn’t entirely off the mark in some cases. But it’s also a gross over-simplification, and a generalization that isn’t doing the hobby any favors when it comes to bringing in new blood.
In reality, a modern ham’s toolkit includes a wide array of technologies that are about as far away from your grandfather’s kit-built rig as could be — and there’s exciting new protocols and tools on the horizon. To ensure a bright future for amateur radio, these technologies need to be nurtured the word needs to be spread about what they can do. Along the way, we’ll also need to push back against stereotypes that can hinder younger operators from signing on.
On the forefront of these efforts is Amateur Radio Digital Communications (ARDC), a private foundation dedicated to supporting amateur radio and digital communication by providing grants to scholarships, educational programs, and promising open source technical projects. For this week’s Hack Chat, ARDC Executive Director Rosy Schechter (KJ7RYV) and Staff Lead John Hays (K7VE) dropped by to talk about the future of radio and digital communications.
Rosy kicked things off with a brief overview of ARDC’s fascinating history. The story starts in 1981, when Hank Magnuski had the incredible foresight to realize that amateur radio packet networks could benefit from having a dedicated block of IP addresses. In those early days, running out of addresses was all but unimaginable, so he had no trouble securing 16.7 million IPs for use by licensed amateur radio operators. This block of addresses, known as AMPRNet and then later 44Net, was administered by volunteers until ARDC was formed in 2011 and took over ownership. In 2019, the decision was made to sell off about four million of the remaining IP addresses — the proceeds of which went into an endowment that now funds the foundation’s grant programs.
Of all the recipients of ARDC grants, the M17 project garnered the most interest during the Chat. This community of open source developers and radio enthusiasts is developing a next-generation digital radio protocol for data and voice that’s unencumbered by patents and royalties. In their own words, M17 is focused on “radio hardware designs that can be copied and built by anyone, software that anyone has the freedom to modify and share to suit their own needs, and other open systems that respect your freedom to tinker.” They’re definitely our kind of folks — we first covered the project in 2020, and are keen to see it develop further.
John says the foundation has approximately $6 million each year they can dole out, and that while there’s certainly no shortage of worthwhile projects to support as it is, they’re always looking for new applicants. The instructions and guides for grant applications are still being refined, but there’s at least one hard requirement for any project that wants to be funded by the ARDC: it must be open source and available to the general amateur population.
Of course, all this new technology is moot if there’s nobody to use it. It’s no secret that getting young people interested in amateur radio has been a challenge, and frankly, it’s little surprise. When a teenager can already contact anyone on the planet using the smartphone in their pocket, getting a ham license doesn’t hold quite the same allure as it did to earlier generations.
Depending on how old you are, this might have been one of the most shocking moments in Stranger Things.
The end result is that awareness among youth is low. During the Chat, one participant recounted how he had to put Netflix’s Stranger Things on pause so he could explain to his teenage son how the characters in the 1980s set show were able to communicate across long distances using a homemade radio. Think about that for a minute — in a show about nightmarish creatures invading our world from an alternate dimension, the hardest thing for this young man to wrap his head around was the fact a group of teenagers would be able to keep in touch with each other without the Internet or phone lines to connect them.
So its no surprise that John says the ARDC is actively looking for programs which can help improve the demographics of amateur radio. The foundation is looking to not only bring younger people onboard, but also reach out to groups that have been traditionally underrepresented in the hobby. As an example, he points to a grant awarded to the Bridgerland Amateur Radio Club (BARC) last year to bolster their youth engagement program. Funds went towards putting together a portable rig that would allow students to communicate with the International Space Station, and the development of hands-on workshops where teens will be able to launch, track, and recover payloads on a high altitude balloon. Let’s see them do that on their fancy new smartphone.
We want to not only thank Rosy Schechter and John Hays for taking part in this week’s Hack Chat, but everyone else at Amateur Radio Digital Communications for their efforts to support the present and future of amateur radio and digital communication.
The Hack Chat is a weekly online chat session hosted by leading experts from all corners of the hardware hacking universe. It’s a great way for hackers connect in a fun and informal way, but if you can’t make it live, these overview posts as well as the transcripts posted to Hackaday.io make sure you don’t miss out.
It’s not immediately clear to us why one would need a mouse for the original PlayStation (though we’re sure there’s no shortage of folks eager to jump down into the comments and tell us), but if you ever desire adding improved pointing capabilities to the nearly three decade old console, this project from [Vojtěch Salajka] is certainly one to keep an eye on.
The aptly named “USB to PlayStation Mouse” project does exactly what it sounds like — adapts a generic USB mouse into an input device for Sony’s classic console. Putting one together requires a Raspberry Pi Pico, a 5 V DC-DC USB boost module with female USB-A connector, and a sacrificial controller or peripheral to provide the cable and proprietary connector.
With the hardware assembled per the simple wiring diagram, you just plug the Pico into your computer and copy over the firmware file. [Vojtěch] notes that you’ll need to unplug the mouse before attempting to upload the firmware, presumably because the data pins on the two USB ports have been tied together.
Don’t worry about having to find some obscure title to try out your new peripheral either, [Vojtěch] says the mouse works in the system’s main menu if you boot it without a disc in the drive. Now all you need is a few Raspberry Pi Pico PlayStation Memory Cards to complete the whole set.
