Apple’s Vision Pro augmented reality goggles made a big splash in the news this week, and try as we might to resist the urge to dunk on them, early adopters spotted in the wild are making it way too easy. Granted, we’re not sure how many of these people are actually early adopters as opposed to paid influencers, but there was still quite a bit of silliness to be had, most of it on X/Twitter. We’d love to say that peak idiocy was achieved by those who showed themselves behind the wheels of their Teslas while wearing their goggles, with one aiming for an early adopter perfecta, but alas, most of these stories appear to be at least partially contrived. Some people were spotted doing their best to get themselves killed, others were content to just look foolish, especially since we’ve heard that the virtual keyboard is currently too slow for anything but hunt-and-peck typing, which Casey Niestat seemed to confirm with his field testing. After seeing all this, we’re still unsure why someone would strap $4,000 worth of peripheral-vision-restricting and easily fenced hardware to their heads, but hey — different strokes. And for those of you wondering why these things are so expensive, we’ve got you covered.
Slider5072 Articles
One Project At A Time, Or A Dozen?
We got a bunch of great food for thought in this week’s ask-us-anything on the Hackaday Podcast, and we all chewed happily. Some of my favorite answers came out of the question about how many projects we all take on at once. Without an exception, the answer was “many”. And while not every one of the projects that we currently have started will eventually reach the finish line, that’s entirely different from saying that none of them ever do. On the contrary, Tom Nardi made the case for having a number of irons simultaneously in the fire.
We all get stuck from time to time. That’s just the nature of the beast. The question is whether you knuckle down and try to brute-force power your way through the difficulty, or whether you work around it. A lot of the time, and this was Dan Maloney’s biggest bugaboo, you lack the particular part or component that you had in mind to get the job done. In that situation, sometimes you just have to wait. And what are you going to do while waiting? Work on Project B! (But take good notes of the state of Project A, because that makes it a lot easier to get back into the swing of things when the parts do arrive.)
Al and I both weighed in on the side of necessity, though. Sometimes, no matter how many attractive other projects you’ve got piled up, one just needs to get out the door first. My recent example was our coffee roaster. Before I start a big overhaul, I usually roast a couple days’ worth of the evil bean. And then the clock starts ticking. No roasting equals two unhappy adults in this household, so it’s really not an option. Time pressure like that helps focus the mind on the top-priority project.
But I’m also with Tom. It’s a tremendous luxury to have a handful of projects in process, and be able to hack on one simply because you’re inspired, or in love with the project at that moment. And when the muse calls, the parts arrive, or you finally figure out what was blocking you on Project A, then you can always get back to it.
How Airplanes Mostly Stopped Flying Into Terrain And Other Safety Improvements
We have all heard the statistics on how safe air travel is, with more people dying and getting injured on their way to and from the airport than while traveling by airplane. Things weren’t always this way, of course. Throughout the early days of commercial air travel and well into the 1980s there were many crashes that served as harsh lessons on basic air safety. The most tragic ones are probably those with a human cause, whether it was due to improper maintenance or pilot error, as we generally assume that we have a human element in the chain of events explicitly to prevent tragedies like these.
Among the worst pilot errors we find the phenomenon of controlled flight into terrain (CFIT), which usually sees the pilot losing track of his bearings due to a variety of reasons before a usually high-speed and fatal crash. When it comes to keeping airplanes off the ground until they’re at their destination, here ground proximity warning systems (GPWS) and successors have added a layer of safety, along with stall warnings and other automatic warning signals provided by the avionics.
With the recent passing of C. Donald Bateman – who has been credited with designing the GPWS – it seems like a good time to appreciate the technology that makes flying into the relatively safe experience that it is today.
Continue reading “How Airplanes Mostly Stopped Flying Into Terrain And Other Safety Improvements”
In Defense Of Anthropomorphizing Technology
Last week I was sitting in a waiting room when the news came across my phone that Ingenuity, the helicopter that NASA put on Mars three years ago, would fly no more. The news hit me hard, and I moaned when I saw the headline; my wife, sitting next to me, thought for sure that my utterance meant someone had died. While she wasn’t quite right, she wasn’t wrong either, at least in my mind.
As soon as I got back to my desk I wrote up a short article on the end of Ingenuity‘s tenure as the only off-Earth flying machine — we like to have our readers hear news like this from Hackaday first if at all possible. To my surprise, a fair number of the comments that the article generated seemed to decry the anthropomorphization of technology in general and Ingenuity in particular, with undue harshness directed at what some deemed the overly emotional response by some of the NASA/JPL team members.
Granted, some of the goodbyes in that video are a little cringe, but still, as someone who seems to easily and eagerly form attachments to technology, the disdain for an emotional response to the loss of Ingenuity perplexed me. That got me thinking about what role anthropomorphization might play in our relationship with technology, and see if there’s maybe a reason — or at least a plausible excuse — for my emotional response to the demise of a machine.
Continue reading “In Defense Of Anthropomorphizing Technology”
Human-Interfacing Devices: Packing For The Descriptor Heist
We started with figuring out HID descriptors a week ago, and I’ve shown you how to send raw HID packets using a MicroPython fork. We do still have the task in front of us – making a touchscreen device. For that, let’s give you the tools to capture an existing descriptor from a touchscreen, then show you how to tweak it and how it turns out in the end.
Packing For The Heist
When it comes to this kind of adventure, we can’t go without tools and weapons – it could be dangerous! Without them, you could even abandon your project halfway! Here’s enough high-precision tools and ammunition to last you through whatever obstacles you might encounter. Except for the web-based tools, these tools are for Linux, but please remember that you can always use a virtual machine or a Raspberry Pi. Nobody would use Windows for a heist anyway, what’s with all the telemetry and such.
The first tool is for reading descriptors – we need one to learn from, it’s just like a keycard you can flash to a security guard and scan at the vault entry. Of course, with RFID, you want to have enough examples, compare bits between a few cards and all. For now, HID descriptors don’t have authenticity checks, but it looks like that might just change in the future. Leave it to Apple and Microsoft to add them, as usual. On Linux, seeing descriptors is simple – as root, go into /sys/bus/usb/devices/, find your device by its lsusb device tree path, then follow the directory with the VID/PID in it. That directory will contain a report_descriptor file – hexdump it. The entire command could look like this:
sudo hexdump -v -e '/1 "%02X "' /sys/bus/usb/devices/3-6.2/3-6.2\:1.1/0003\:0C40\:8000.0022/report_descriptor
Again, you might need root to even find this path, so use sudo -i if you must. The format string in the hexdump command gives you parser-friendly output. Specifically, for parsing, I use this webpage – it’s wonderful, even adding tabs that delineate different sections of the descriptor, making its output all that more readable! You can also save this webpage locally, it’s a very neat tool. Other than that, you can try other local tools like this one!
Continue reading “Human-Interfacing Devices: Packing For The Descriptor Heist”
They Want To Put A Telescope In A Crater On The Moon
When we first developed telescopes, we started using them on the ground. Humanity was yet to master powered flight, you see, to say nothing of going beyond into space. As technology developed, we realized that putting a telescope up on a satellite might be useful, since it would get rid of all that horrible distortion from that pesky old atmosphere. We also developed radio telescopes, when we realized there were electromagnetic signals beyond visible light that were of great interest to us.
Now, NASA’s dreaming even bigger. What if it could build a big radio telescope up on the Moon?
Continue reading “They Want To Put A Telescope In A Crater On The Moon”
Hackaday Links: February 4, 2024
Things may not have gone as planned last week for the flying cellphone on Mars, but just because Ingenuity‘s flying career is over doesn’t mean there’s no more work to do. NASA announced this week that it’s going to try a series of “wiggle” maneuvers on Ingenuity‘s rotors, in an attempt to get a better look at the damage to the blade tips and possibly get some clues as to what went wrong. The conjecture at the moment seems to be that a large area of relatively featureless terrain confused the navigation system, which uses down-facing cameras to track terrain features. If the navigation program couldn’t get a bead on exactly how far above the ground it was, it’s possible the copter came in too hard and caused the rotor tips to dig into the regolith. There seems to be some photographic suggestion of that, with what looks like divots in the ground about where you’d expect the rotor tips to dig in, and even scraps of material that look out of place and seem to be about the same color as the rotor blades. All this remains to be seen, of course, and we’re sure that NASA and JPL are poring over all available data to piece together what happened. As much as we hate to say goodbye to Ingenuity, we eagerly await the post-mortem.





