I heard a “Year in Review” program the other day on NPR with a BBC World Service panel discussion of what’s ahead for 2017. One prediction was that UAV delivery of packages would be commonplace this year, and as proof the commentator reported that Amazon had already had a successful test in the UK. But he expressed skepticism that it would ever be possible in the USA, where he said that “the first drone that goes over somebody’s property will be shot down and the goods will be taken.”
He seemed quite sincere about his comment, but we’ll give him the benefit of the doubt that he was only joking to make a point, not actually grotesquely ignorant about the limitations of firearms or being snarky about gun owners in the US. Either way, he brings up a good point: when autonomous parcel delivery is commonplace, who will make sure goods get to the intended recipient?
As a Hackaday writer, you can never predict where the comments of your posts will go. Some posts seem to be ignored, while others have a good steady stream of useful feedback. But sometimes the comment threads just explode, heading off into seemingly uncharted territory only tangentially related to the original post.
Such was the case with [Steven Dufresne]’s recent post about decimal time, where the comments quickly became a heated debate about the relative merits of metric and imperial units. As I read the thread, I recalled any of the numerous and similarly tangential comments on various reddit threads bashing the imperial system, and decided that enough was enough. I find the hate for the imperial system largely unfounded, and so I want to rise to its defense.
Rotary encoders are great devices. Monitoring just a few pins you can easily and quickly read in rotation and direction of a user input (as well as many other applications). But as with anything, there are caveats. I recently had the chance to dive into some of the benefits and drawbacks of rotary encoders and how to work with them.
I often work with students on different levels of electronic projects. One student project needed a rotary encoder. These come in mechanical and optical variants. In a way, they are very simple devices. In another way, they have some complex nuances. The target board was an ST Nucleo. This particular board has a small ARM processor and can use mbed environment for development and programming. The board itself can take Arduino daughter boards and have additional pins for ST morpho boards (whatever those are).
The mbed system is the ARM’s answer to Arduino. A web-based IDE lets you write C++ code with tons of support libraries. The board looks like a USB drive, so you download the program to this ersatz drive, and the board is programmed. I posted an intro to mbed awhile back with a similar board, so if you want a refresher on that, you might like to read that first.
Reading the Encoder
The encoder we had was on a little PCB that you get when you buy one of those Chinese Arduino 37 sensor kits. (By the way, if you are looking for documentation on those kinds of boards, look here.; in particular, this was a KY-040 module.) The board has power and ground pins, along with three pins. One of the pins is a switch closure to ground when you depress the shaft of the encoder. The other two encode the direction and speed of the shaft rotation. There are three pull-up resistors, one for each output.
I expected to explain how the device worked, and then assist in writing some code with a good example of having to debounce, use pin change interrupts, and obviously throw in some other arcane lore. Turns out that was wholly unnecessary. Well… sort of.
Here at Hackaday we are a diverse bunch, we all bring our own experience to the task of bringing you the best of the hardware scene. Our differing backgrounds were recently highlighted by a piece from my colleague [Dan] in which he covered the teardown of a cordless electric chainsaw.
It was his line “Now, we’d normally shy away from any electric chainsaw, especially a cordless saw, and doubly so a Harbor Freight special“. that caught my eye. I’m with him on cordless tools which I see as a cynical ploy from manufacturers to ensure 5-yearly replacements, and I agree that cheap tools are a false economy. But electric chainsaws? Here on this small farm, they’re the saw of choice and here’s why.
What are the evocative sounds and smells of your childhood? The sensations that you didn’t notice at the time but which take you back immediately? For me one of them is the slight smell of phenolic resin from an older piece of consumer electronics that has warmed up; it immediately has me sitting cross-legged on our living room carpet, circa 1975.
That phenolic smell has gone from our modern electronics, not only because modern enclosures are made from ABS and other more modern plastics, but because the electronics they contain no longer get so hot. Our LCD TV for instance nowadays uses only 50 watts, while its 1970s CRT predecessor would have used several hundred. Before the 1970s you would not find many household appliances that used less than 100 watts, but if you take stock of modern electrical appliances, few use more than that. Outside the white goods in your kitchen and any electric heaters or hair dryers you may own, your appliances today are low-powered. Even your lighting is rapidly being taken over by LEDs, which are at their heart low-voltage devices.
There are many small technological advancements that have contributed to this change over the decades. Switch-mode power supplies, LCD displays, large-scale integration, class D audio and of course the demise of the thermionic tube, to name but a few. The result is often that the appliance itself runs from a low voltage. Where once you would have had a pile of mains plugs competing for your sockets, now you will have an equivalent pile of wall-wart power supplies. Even those appliances with a mains cord will probably still contain a switch-mode power supply inside.
Our hackspace has acquired an Amazon Dot, courtesy of a member. It mostly seems to be used as a source of background music, but it has also spawned a seemingly never-ending new entertainment in which the hackspace denizens ceaselessly bait their new electronic companion with ever more complex and esoteric requests. From endless rephrasing and careful enunciation of obscure early reggae artists to try to settle a musical argument to hilarious mis-hearing on the part of our silicon friend, the fun never stops. “Alexa, **** off!” it seems results in “I’m sorry, I can’t find a device of that name on this network”.
Fair enough, you might say, we’re always early adopters of any new technology. But it’s a development over which I wonder; am I alone in finding it surprising? It’s worth taking a moment to look at the subject.
In Texas — at least around Houston — we don’t have basements. We do, however, have bilges. Both of these are subject to taking on water when no one is paying attention. A friend of mine asked me what I thought of an Instructable that showed how to make a water sensor using a few discrete components. The circuit would probably work — it relied on the conductivity of most water to supply enough current to a bipolar transistor’s base to turn it on.
It is easy to overthink something like this, so I told my friend he should go with something a little more old-fashioned. I don’t know the origin of it, but it is older than I am. You can make a perfectly good water detector with things you probably already have around the house. My point isn’t that you should (or shouldn’t) construct a homemade water sensor. My point is that you don’t always need to go to the high-tech solution.