RFID is a workhorse in industrial, commercial, and consumer markets. Passive tags, like work badges and key fobs, need a base station but not the tags. Sensors are a big market and putting sensors in places that are hard to reach, hostile, or mobile is a costly proposition. That price could drop, and the sensors could be more approachable with help from MIT’s Auto-ID Lab who are experimenting with sensor feedback to RFID devices.
Let’s pretend you want to measure the temperature inside a vat of pressurized acid. You’d rather not drill a hole in it to insert a thermometer, but a temperature sensor sealed in Pyrex that wirelessly transmits the data and never runs out of power is a permanent and cheap solution. The researchers have their sights set on glucose sensing and that news come shortly after Alphabet gave up their RFID quest to measure glucose through contact lenses. Shown the top of this article is a prototype for a Battery Assisted Passive (BAP) RFID sensor that uses commodity glucose testing strips, sending data when the electrochemical reaction occurs. It uses six of these cells in parallel to achieve a high enough peak current to trigger the transmission. But the paper (10.1109/RFID.2018.8376201 behind paywall) mentions a few strategies to improve upon this. However, it does prove the concept that the current spike from the test strips determines the time the tag is active and that can be correlated to the blood glucose detected.
How many of our own projects would instantly upgrade with the addition of a few sensors that were previously unobtainable on a hacker budget? Would beer be brewed more effectively with more monitoring? How many wearables would be feasible with battery-free attachments? The sky is the figurative limit.
[GlytchTech] decided to implement his own Digital Data Link (DDL) for his drone experiments, and by using a Raspberry Pi Zero and some open-source software, he succeeded in creating a mostly self-contained system that delivers HD video and telemetry using an Android phone as a display.
USB tethered Android phone used as a display and touch interface.
The link uses standard WiFi hardware in a slightly unusual way to create a digital data link that acts more like an analog system, with a preference for delivering low latency video and a graceful drop-off when signal quality gets poor. A Raspberry Pi Zero, Alfa NEH WiFi card, external antenna, battery, and a 3D printed enclosure result in a self-contained unit. Two are needed: one for each end of the link. One unit goes on the drone and interfaces to the flight controller, and the other is for the ground station.
A companion android app allows for just about any old Android phone to serve as video feed, on-screen display of telemetry data, and touchscreen interface.
The software is DroneBridge (GitHub repository) and it implements Wifibroadcast which uses WiFi radios, but without the usual WiFi functionality. A Raspberry Pi is the usual platform, but there’s also an ESP32 port. The software is capable of even more, but so far suits [GlytchTech]’s needs just fine, and he was able to refine his original Watch_Dogs-inspired hacking drone with it.
Bees. The punchline to the title is bees carrying sensors like little baby bee backpacks. We would run out of fingers counting the robots which emulate naturally evolved creatures, but we believe there is a lot of merit to pirating natural designs, but researchers at the University of Washington cut out the middle-man and put their sensors right on living creatures. They measured how much a bee could lift, approximately 105 milligrams, then built a sensor array lighter than that. Naturally, batteries are holding back the design, and the rechargeable lithium-ion is more than half of the weight.
When you swap out brushless motors for organics, you gain and lose some things. You lose the real-time control, but you increase the runtime. You lose the noise, but you also lose the speed. You increase the range, but you probably wind up visiting the same field over and over. If your goal is to monitor the conditions of flowering crops, you may be ready to buy and install, but for the rest of us, dogs are great for carrying electronics. Oh yes. Cats are not so keen. Oh no.
The story goes that Atari was developing a premium model of their popular home video game console, the Atari 2600, for the 1981 fiscal year. Internally known as the Stella RC, this model revision promised touch sensitive game selection toggles, LED indicators, and onboard storage for the controllers. The focus of the project, however, was the “RC” in Stella RC which stood for remote control. Atari engineers wanted to free players from the constraints of the wires that fettered them to their televisions.
Problem with the prototypes was that the RF transmitters in the controllers were powerful enough to send a signal over a 1000 ft. radius, and they interfered with a number of the remote garage door openers on the market. Not to mention that if there were another Stella RC console on the same channel in an apartment building, or simply across the street, you could be playing somebody else’s Pitfall run. The mounting tower of challenges to making a product that the FCC would stamp their approval on were too great. So Atari decided to abandon the pioneering Stella RC project. Physical proof of the first wireless game controllers would have been eliminated at that point if it were created by any other company… but prototypes mysteriously left the office in some peculiar ways.
“Atari had abandoned the project at the time…[an Atari engineer] thought it would be a great idea to give his girlfriend’s son a videogame system to play with…I can’t [comment] about the relationship itself or what happened after 1981, but that’s how this system left Atari…and why it still exists today.”
– Joe Cody, Atari2600.com
Atari did eventually get around to releasing some wireless RF 2600 joysticks that the FCC would approve. A couple years after abandoning the Stella RC project they released the Atari 2600 Remote Control Joysticks at a $69.95 MSRP (roughly $180 adjusted for inflation). The gigantic price tag mixed with the video game market “dropping off the cliff” in 1983 saw few ever getting to know the bliss of wire-free video game action. It was obvious that RF game controllers were simply ahead of their time, but there had to be cheaper alternatives on the horizon.
Out of Sight, Out of Control with IR Schemes
Nintendo AVS console deck and IR controller on display.
Video games were a dirty word in America in 1985. While games themselves were still happening on the microcomputer platforms, the home console business was virtually non-existent. Over in Japan, Nintendo was raking in money hand over fist selling video games on their Famicom console. They sought to replicate that success in North America by introducing a revised model of the Famicom, but it had to impress the tech journos that would be attending its reveal at the Consumer Electronics Show (CES).
The prototype system was called the Nintendo Advanced Video System (AVS). It would feature a keyboard, a cassette tape drive, and most importantly two wireless controllers. The controllers used infrared (IR) communication and the receiver was built-into the console deck itself. Each controller featured a square metallic directional pad and four action buttons that gave the impression of brushed aluminum. The advancement in video game controller technology was too good to be true though, because the entire system received a makeover before releasing as the Nintendo Entertainment System (NES) that Christmas. The NES lacked the keyboard, the tape drive, and the IR controllers and its change in materials hardly captured the high-end flash of the AVS. The removal of IR meant the device was cheaper to manufacture. A decision that ultimately helped the NES to become a breakout success that in turn brought back dedicated video game consoles single-handedly.
Making wine isn’t just about following a recipe, it’s a chemical process that needs to be monitored and managed for best results. The larger the batch, the more painful it is to have something go wrong. This means that the stakes are high for small vineyards such as the family one [Mare] works with, which have insufficient resources to afford high-end equipment yet have the same needs as larger winemakers. The most useful thing to monitor is the temperature profile of the fermentation process, and [Mare] created an exceptional IoT system to do that using LoRa wireless and solar power.
It’s not enough just to measure temperature of the fermenting liquid; viewing how the temperature changes over time is critical to understanding the process and spotting any trouble. [Mare] originally used a Raspberry Pi, I2C temperature sensor, and a Wi-Fi connection to a database to do the monitoring. This was a success, but it was also overkill. To improve the system, the Raspberry Pi was replaced with a LoRaDunchy board, an STM-based module of [Mare]’s own design which is pin-compatible with the Arduino Nano. It includes a battery charger, power management, and LoRa wireless communication. Adding a solar cell and lithium-polymer battery was all it took to figuratively cut the power cord.
Sensing the temperature of fermentation is done by sealing the temperature sensor into a thin aluminum tube, and lowering that into the vat. There it remains, with the LoRaDunchy board periodically waking up to read the sensor and report the tempurature over LoRa before going back to sleep, all the while sipping power from the battery which in turn gets recharged with solar power.
It’s an elegant system that has already paid off. A 500 litre vat of wine generated an alarm when the temperature rose above 24 Celsius for 10 minutes. An email alert allowed the owner to begin mixing the solution and add ice water to put the brakes on the runaway reaction. The temperature dropped and slow fermentation resumed, thanks to the twin powers of gathering the right data, then doing something meaningful with it.
Vineyards and LoRa have joined forces before, for example in the Vinduino project which aims to enable water-smart farming. If you’re unfamiliar with LoRa in general, the LoRa on the ESP32 project page contains a good primer, and if the antenna on the module shown here looks familiar to you it’s because we recently featured [Mare]’s guide on making DIY LoRa antennas from salvaged wire.
[Mare] has a visual guide and simple instructions for making DIY mini helical 868 MHz antennas for LoRa applications. 868 MHz is a license-free band in Europe, and this method yields a perfectly serviceable antenna that’s useful where space is constrained.
A metric 5 mm drill bit makes a convenient core.
The process is simple and well-documented, but as usual with antenna design it requires attention to detail. Wire for the antenna is silver-plated copper, salvaged from the core of RG214U coaxial cable. After straightening, the wire is wound tightly around a 5 mm core. 7 turns are each carefully spaced 2 mm apart. After that, it’s just a matter of measuring and bending the end for soldering to the wireless device in question. [Mare] has used this method for wireless LoRa sensors in space-constrained designs, and it also has the benefit of lowering part costs since it can be made and tested in-house.
Antennas have of course been made from far stranger things than salvaged wire; one of our favorites is this Yagi antenna made from segments of measuring tape.
Hackaday regular [befinitiv] wrote into the tip line to let us know about a hack you might enjoy, wireless UART output from a bare STM32 microcontroller. Desiring the full printf debugging experience, but constrained both by available space and expense, [befinitiv] was inspired to improvise by a similar hack that used the STM32 to send Morse code over standard FM frequencies.
In this case, [befinitiv]’s solution is both more useful and slightly more legal, as the software uses the 27 MHz ISM band to blast out ASK modulated serial data through a simple wire antenna attached to one of the microcontroller’s pins. The broadcast can then be picked up by an RTL-SDR receiver and interpreted back into a stream of data by GNU Radio.
The software for the STM32 and the GNU Radio Companion graph are both available on Bitbucket. The blog post goes into some detail explaining how the transmitter works and what all the GNU Radio components are doing to claw the serial data back from the ether.
Let’s pretend you want to measure the temperature inside a vat of pressurized acid. You’d rather not drill a hole in it to insert a thermometer, but a temperature sensor sealed in Pyrex that wirelessly transmits the data and never runs out of power is a permanent and cheap solution. The researchers have their sights set on glucose sensing and that news come shortly after Alphabet gave up their RFID quest to measure glucose through contact lenses. Shown the top of this article is a prototype for a Battery Assisted Passive (BAP) RFID sensor that uses commodity glucose testing strips, sending data when the electrochemical reaction occurs. It uses six of these cells in parallel to achieve a high enough peak current to trigger the transmission. But the paper (10.1109/RFID.2018.8376201 behind paywall) mentions a few strategies to improve upon this. However, it does prove the concept that the current spike from the test strips determines the time the tag is active and that can be correlated to the blood glucose detected.
