When [DonHo] sang about tiny bubbles, he probably wasn’t thinking of them embedded in glycerine. But that’s where the bubbles in [ShinodaY]’s clock reside. The viscous fluid holds the bubbles better allowing the time to be read more easily. You can watch the relaxing display in the video below.
The theory of operation is simple and reminds us somehow of a reverse Tetris game. Solenoid valves at the base release air bubbles to form a row of the display. The bubbles rising makes room for the next row. The display has as many columns as there are air outlets at the bottom. Spacing the bubble pixels is as simple as adjusting the timing between air bubbles.
After a decade in development, the Boeing CST-100 “Starliner” lifted off from pad SLC-41 at the Cape Canaveral Air Force Station a little before dawn this morning on its first ever flight. Officially referred to as the Boeing Orbital Flight Test (Boe-OFT), this uncrewed mission was intended to verify the spacecraft’s ability to navigate in orbit and safely return to Earth. It was also planned to be a rehearsal of the autonomous rendezvous and docking procedures that will ultimately be used to deliver astronauts to the International Space Station; a capability NASA has lacked since the 2011 retirement of the Space Shuttle.
Liftoff at 6:36 AM Eastern
Unfortunately, some of those goals are now unobtainable. Due to a failure that occurred just 30 minutes into the flight, the CST-100 is now unable to reach the ISS. While the craft remains fully functional and in a stable orbit, Boeing and NASA have agreed that under the circumstances the planned eight day mission should be cut short. While there’s still some hope that the CST-100 will have the opportunity to demonstrate its orbital maneuverability during the now truncated flight, the primary focus has switched to the deorbit and landing procedures which have tentatively been moved up to the morning of December 22nd.
While official statements from all involved parties have remained predictably positive, the situation is a crushing blow to both Boeing and NASA. Just days after announcing that production of their troubled 737 MAX airliner would be suspended, the last thing that Boeing needed right now was another high-profile failure. For NASA, it’s yet another in a long line of setbacks that have made some question if private industry is really up to the task of ferrying humans to space. This isn’t the first time a CST-100 has faltered during a test, and back in August, a SpaceX Crew Dragon was obliterated while its advanced launch escape system was being evaluated.
We likely won’t have all the answers until the Starliner touches down at the White Sands Missile Range and Boeing engineers can get aboard, but ground controllers have already started piecing together an idea of what happened during those first critical moments of the flight. The big question now is, will NASA require Boeing to perform a second Orbital Flight Test before certifying the CST-100 to carry a human crew?
Let’s take a look at what happened during this morning’s launch.
The Numitron was a type of display popular in the 1970s, and often used in aircraft avionics and other high-end hardware. The display is a 7-segment type, but using filaments instead of LEDs. [sjm4306] was able to lay his hands on four of these devices, along with some bulbs to act as the digit seperator and AM/PM indicator. Due to being incandescent in nature, multiplexing wasn’t a practical option, with lower duty cycles drastically dimming the display. Instead, a 32-bit cascaded shift register was used to enable all the segments to be driven at the same time.
It’s a great build that uses some genuine original display hardware to create a clock with a compelling vintage aesthetic. This would make a great gift to a pilot from the era, or any hacker that likes the unusual display technologies of yesteryear. You can even build a Numitron watch, if you’re so inclined. Video after the break.
We’ve all seen the IoT device security trainwrecks: those gadgets that fail so spectacularly that the comment section lights up with calls of “were they even thinking about the most basic security?” No, they probably weren’t. Are you?
Hackaday Contributor and all around good guy Kerry Scharfglass thinks about basic security for a living, and his talk is pitched at the newcomer to device security. (Embedded below.) Of course “security” isn’t a one-size-fits-all proposition; you need to think about what threats you’re worried about, which you can ignore, and defend against what matters. But if you’ve never worked through such an exercise, you’re in for a treat here. You need to think like a maker, think like a breaker, and surprisingly, think like an accountant in defining what constitutes acceptable risks. Continue reading “Kerry Scharfglass Secures Your IoT Things”→
Macros are meant to make our lives easier, but they live up to this promise with mixed results. Generally speaking, a macro is a special combination of keys on the keyboard that execute a custom task — their goal is to speed up your productivity by getting away from mousing through menus. But once a macro requires more than two keys, they can get a bit cumbersome to input. I have personally found that repeated use of macros that require ctrl+shift can potentially cause problems. I don’t know about you (and your repetitive stress mileage may vary), but personal injury is the polar opposite of what I want from something that’s supposed to be convenient.
I love keyboard shortcuts, and not just because I prefer keyboard navigation in general. A lot of little things about writing for the web can be streamlined with shortcuts, like writing html tags and doing image manipulation. And I’m always looking for a better workflow to pin down my fleeting mental fragments, at least until that dark day that I can turn on Dropbox Thoughts™ and burn my brainwaves directly to disk.
Hackaday editors Mike Szczys and Elliot Williams get together for the 47th and final Hackaday Podcast of 2019. We dive into the removable appendix on Prusa’s new “Buddy” control board, get excited over the world’s largest grid-backup battery, and commiserate about the folly of designing enclosures as an afterthought. There’s some great research into which threaded-inserts perform best for 3D-printed parts, how LEDs everywhere should be broadcasting data, and an acoustic organ that’s one-ups the traditional jug band.
Take a look at the links below if you want to follow along, and as always tell us what you think about this episode in the comments!
Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
The SDR revolution has brought a bonanza of opportunities for experimentation to the radio enthusiast, but with it has come a sometimes-confusing array of software for which even installation can be a difficult prospect for an SDR novice. If you’re bamboozled by it all then help may be at hand courtesy of [Luigi Cruz], who has packaged a suite of ready-to-go popular SDR software in an OS image for the Raspberry Pi.
On board the Raspbian-based OS image are SDR Angel, Soapy Remote, GQRX, GNURadio, LimeUtil, and LimeVNA. In hardware terms the RTL-SDR is supported, along with the LimeSDR, PlutoSDR, Airspy, and Airspy HF. All are completely ready-to-go and even have desktop shortcuts, so if the CLI scares you then you can still dive in and play. More importantly it’s designed for use with SDR transmitters as well as receivers, so the barrier for full SDR operation for radio amateurs has become significantly lower too.
This year has seen the seven-year anniversary of the RTL-SDR hack that probably did most to kickstart the use of SDRs in our community. Our colleague [Tom Nardi] wrote a retrospective that’s worth a look for its overview of some SDR tricks that have evolved over that time. Meanwhile if you don’t mind restricting your outlook somewhat, it’s possible to turn the Raspberry Pi 3 into an SDR all without any extra hardware.
