Engineers: Be Subversive To Be Green

The caterers for the volunteer workforce behind the summer’s MCH hacker camp in the Netherlands served all-vegan food. This wasn’t the bean sprouts and lentils that maybe some of the more meat-eating readers might imagine when confronted with vegan food, nor was it a half-as-good array of substitutes with leathery soy hamburgers and rubbery fake cheese smelling suspiciously of feet.

Instead it was a well-crafted, interesting, and tasty menu that was something to look forward to after several hours driving a vanload of handwashing sinks. It was in one of their meals that I found food for thought when driving a week later past the huge Garzweiler open-cast lignite mine on my way through Germany to Luxembourg’s Haxogreen as part of my European hacker camp summer tour.

The meal was deep-fried soy protein strips and the mine is probably one of Western Europe’s dirtiest and most problematic CO2 sources in a country that likes to imagine itself as environmentally friendly, so where in this unlikely connection did I find a pairing? Continue reading “Engineers: Be Subversive To Be Green”

The State Of The SBC Interface Ecosystem, Is It Time To Design A Standard?

We are spoiled for choice when it comes to single board computers, whether they be based around a microcontroller or a more capable SoC capable of running an operating system such as GNU/Linux. They can be had from well-established brands such as Arduino, Adafruit, or Raspberry Pi, or from a Wild West of cheaper Far Eastern modules carrying a plethora of different architectures.

Everyone has their own favourite among them, and along with that comes an ecosystem of operating systems and software development environments. There’s another aspect to these boards which has evolved; certain among them have become de facto interface connector standards for hardware peripherals. Do these standards make any sense? Let’s talk about that.

Continue reading “The State Of The SBC Interface Ecosystem, Is It Time To Design A Standard?”

Big Brother Or Dumb Brother? Bus Drivers In Beijing Are Forced To Wear “Emotional Monitors”

Humans aren’t always great at respecting each other’s privacy. However, common sense says there’s a clear boundary when it comes to the thoughts in one’s own head and the feelings in one’s heart.

For bus drivers in Beijing though, it seems that’s no longer the case. These professional drivers are now being asked to wear emotional monitors while on the job, raising concerns from both legal and privacy advocates. But the devices aren’t really anything more than workout monitors, and whether they can actually make good on their Orwellian promise remains to be seen.

In Your Head, In Your Head!

The monitoring wristbands have been rolled out to some of Beijing’s long-distance bus drivers. Credit: Cypp0847, CC-BY-SA-4.0

When George Orwell wrote 1984, it was only 1949. However, he was able to foresee a world in which surveillance was omnipresent and inescapable. He also envsioned the concept of thoughtcrime, where simply contemplating the wrong things could get you in serious trouble with the authorities.

As we all know, Orwell was way off – these predictions didn’t become reality until well into the 2000s. In the latest horrifying development, technologies now exist that claim to be able to monitor one’s emotional state. Now, China’s transportation sector is rushing to push them on their workforces.

Long-distance bus drivers in Beijing are now being told to wear electronic wristbands when on the job. These wristbands claim to be able to capture the wearer’s emotional state, monitoring it on behalf of the employer. The scheme was the idea of the Beijing Public Transport Holding Group. The state-run organization claims the technology is intended for the safety of the public, and a trial of the wristbands began in July this year. Continue reading “Big Brother Or Dumb Brother? Bus Drivers In Beijing Are Forced To Wear “Emotional Monitors””

Unintentional Emissions

First, it was the WiFi router: my ancient WRT54G that had given me nearly two decades service. Something finally gave out in the 2.4 GHz circuitry, and it would WiFi no more. Before my tears could dry, our thermometer went on the fritz. It’s one of those outdoor jobbies that transmits the temperature to an indoor receiver. After that, the remote for our office lights stopped working, but it was long overdue for a battery change.

Meanwhile, my wife had ordered a new outdoor thermometer, and it too was having trouble keeping a link. Quality control these days! Then, my DIY coffee roaster fired up once without any provocation. This thing has worked quasi-reliably for ten years, and I know the hardware and firmware as if I had built them myself – there was no way one of my own tremendously sophisticated creations would be faulty. (That’s a joke, folks.) And then the last straw: the batteries in the office light remote tested good.

We definitely had a poltergeist, a radio poltergeist. And the root cause would turn out to be one of those old chestnuts from the early days of CMOS ICs – never leave an input floating that should have a defined logic level. Let me explain.

The WRT54G was the hub of my own home automation system, an accretion of ESP8266 and other devices that all happily speak MQTT to each other. When it went down, none of the little WiFi nodes could boot up right. One of them, described by yours truly in this video, is an ESP8266 connected to a 433 MHz radio transmitter. Now it gets interesting – the thermometers and the coffee roaster and the office lights all run on 433 MHz.

Here’s how it went down. The WiFi-to-433 bridge failed to connect to the WiFi and errored out before the part of the code where it initialized GPIO pins. The 433 MHz transmitter was powered, but its digital input was left flopping in the breeze, causing it to spit out random data all the time, with a pretty decent antenna. This jammed everything in the house, and apparently even once came up with the command to turn on the coffee roaster, entirely by chance. Anyway, unplugging the bridge fixed everything.

This was a fun one to troubleshoot, if only because it crossed so many different devices at different times, some homebrew and some commercial, and all on different control systems. Until I put it together that everything on 433 MHz was failing, I hadn’t even thought of it as one event. And then it turns out to be a digital electronics classic – the dangling input!

Anyway, hope you enjoyed the ride. And spill some copper for the humble pull-down resistor.

Cursing The Curse Of Cursive

Unlike probably most people, I enjoy the act of writing by hand — but I’ve always disliked signing my name. Why is that? I think it’s because signatures are supposed to be in cursive, or else they don’t count. At least, that’s what I was taught growing up. (And I’m really not that old, I swear!)

Having the exact same name as my mother meant that it was important to adolescent me to be different, and that included making sure our signatures looked nothing alike. Whereas her gentle, looping hand spoke to her sensitive and friendly nature, my heavy-handed block print was just another way of letting out my teen angst. Sometime in the last couple of decades, my signature became K-squiggle P-squiggle, which is really just a sped-up, screw-you version of my modern handwriting, which is a combination of print and cursive.

But let’s back up a bit. I started learning to write in kindergarten, but that of course was in script, with separate letters. Me and my fellow Xennial zeigeistians learned a specific printing method called D’Nealian, which was designed to ease the transition from printing to cursive with its curly tails on every letter.

We practiced our D’Nealian (So fancy! So grown-up!) on something called Zaner-Bloser paper, which is still used today, and by probably second grade were making that transition from easy Zorro-like lowercase Zs to the quite mature-looking double-squiggle of the cursive version. It was as though our handwriting was moving from day to night, changing and moving as fast as we were. You’d think we would have appreciated learning a way of writing that was more like us — a blur of activity, everything connected, an oddly-modular alphabet that was supposed to serve us well in adulthood. But we didn’t. We hated it. And you probably did, too.

Continue reading “Cursing The Curse Of Cursive”

Honor Your Hacker Heroes

We recently ran an article on a sweet percussion device made by minimal-hardware-synth-madman [Gijs Gieskes]. Basically, it amplifies up an analog meter movement and plays it by slamming it into the end stops. Rhythmically, and in stereo. It’s got that lovely thud, plus the ringing of the springs. It takes what is normally a sign that something’s horribly wrong and makes a soundtrack out of it. I love it.

[Gijs] has been making electro-mechanical musical hacks for about as long as I’ve been reading Hackaday, if not longer. We’ve written up no fewer than 22 of his projects, and the first one on record is from 2005: an LSDJ-based hardware sequencer. All of his projects are simple, but each one has a tremendously clever idea at its core that comes from a deep appreciation of everything going on around us. Have you noticed that VU meters make a particular twang when they hit the walls? Sure you have. Have you built a percussion instrument out of it? [Gijs] has!

Maybe it’s a small realization, and it’s not going to change the world by itself, but I’ve rebuilt more than a couple projects from [Gijs]’ repertoire, and each one has made my life more fun. And if you’re a regular Hackaday reader, you’ve probably seen hundreds or thousands of similar little awesome ideas played out, and maybe even taken some of them on as your own as well. When they accumulate up, I believe they can change the world, at least in the sense of filling up a geek’s life. I hope that feeling comes across when we write up a project. Those of you out there hacking, we salute you!

A Love Letter To Small Design Teams, And The B-52

The true measure of engineering success — or, at least, one of them — is how long something remains in use. A TV set someone designed in 1980 is probably, at best, relegated to a dusty guest room today if not the landfill. But the B-52 — America’s iconic bomber — has been around for more than 70 years and will likely keep flying for another 30 years or more. Think about that. A plane that first flew in 1952 is still in active use. What’s more, according to a love letter to the plane by [Alex Hollings], it was designed over a weekend in a hotel room by a small group of people.

A Successful Design

One of the keys to the plane’s longevity is its flexibility. Just as musicians have to reinvent themselves if they want to have a career spanning decades, what you wanted a bomber to do in the 1960s is different than what you want it to do today. Oddly enough, other newer bombers like the B-1B and B-2 have already been retired while the B-52 keeps on flying.

Continue reading “A Love Letter To Small Design Teams, And The B-52”