Paul Stoffregen did it again: the Teensy 4.0 has been released. The latest in the Teensy microcontroller development board line, the 4.0 returns to the smaller form-factor last seen with the 3.2, as opposed to the larger 3.5 and 3.6 boards.
Don’t let the smaller size fool you; the 4.0 is based on an ARM Cortex M7 running at 600 MHz (!), the fastest microcontroller you can get in 2019, and testing on real-world examples shows it executing code more than five times faster than the Teensy 3.6, and fifteen times faster than the Teensy 3.2. Of course, the new board is also packed with periperals, including two 480 Mbps USB ports, 3 digital audio interfaces, 3 CAN busses, and multiple SPI/I2C/serial interfaces backed with integrated FIFOs. Programming? Easy: there’s an add-on to the Arduino IDE called Teensyduino that “just works”. And it rings up at an MSRP of just $19.95; a welcomed price point, but not unexpected for a microcontroller breakout board.
The board launches today, but I had a chance to test drive a couple of them in one of the East Coast Hackaday labs over the past few days. So, let’s have a closer look.
Continue reading “New Teensy 4.0 Blows Away Benchmarks, Implements Self-Recovery, Returns To Smaller Form”
Somehow [hvde] wound up with a CB radio that does AM and SSB on the 11 meter band. The problem was that the radio isn’t legal where he lives. So he decided to change the radio over to work on the 6 meter band, instead.
We were a little surprised to hear this at first. Most radio circuits are tuned to pretty close tolerances and going from 27 MHz to 50 MHz seemed like quite a leap. The answer? An Arduino and a few other choice pieces of circuitry.
Continue reading “CB Radio + Arduino = 6 Meter Ham Band”
If you treat your Pi as a wearable or a tablet, you will already have a battery. If you treat your Pi as a desktop you will already have a plug-in power supply, but how about if you live where mains power is unreliable? Like [jwhart1], you may consider building an uninterruptible power supply into a USB cable. UPSs became a staple of office workers when one-too-many IT headaches were traced back to power outages. The idea is that a battery will keep your computer running while the power gets its legs back. In the case of a commercial UPS, most generate an AC waveform which your computer’s power supply converts it back to DC, but if you can create the right DC voltage right to the board, you skip the inverting and converting steps.
Cheap batteries develop a memory if they’re drained often, but if you have enough space consider supercapacitors which can take that abuse. They have a lower energy density rating than lithium batteries, but that should not be an issue for short power losses. According to [jwhart1], this quick-and-dirty approach will power a full-sized Pi, keyboard, and mouse for over a minute. If power is restored, you get to keep on trucking. If your power doesn’t come back, you have time to save your work and shut down. Spending an afternoon on a power cable could save a weekend’s worth of work, not a bad time-gamble.
We see what a supercap UPS looks like, but what about one built into a lightbulb or a feature-rich programmable UPS?
Greenhouses create an artificial climate specifically suited to the plants you want to grow. It’s done by monitoring conditions like temperature and humidity, and making changes using things like vents, fans, irrigation, and lighting fixtures to boost temperature. But how do you know when it’s time to up the humidity, or vent some of the heat building up inside? The easy way is to use the Arduino-powered Norman climate simulator from [934Virginia] which leverages data from different locations or times of year based on NOAA weather data to mimic a particular growing environment.
Norman relies on a simple input of data about the target location, working from coordinates and specified date ranges to return minimum/maximum values for temperature and humidity weather conditions. It makes extensive use of the Dusk2Dawn library, and models other atmospheric conditions using mathematical modeling methods in order to make relatively accurate estimates of the target climate. There are some simulations on the project’s Plotly page which show what this data looks like.
This data is used by [934Virginia’s] Arduino library to compare the difference between your target climate and actual sensor readings in your greenhouse. From there you can make manual changes to the environment, or if you’re luck and already have an Arduino-based greenhouse automation system the climate adjustments can be done automatically. The project is named after Norman Borlaug, a famous soil scientist and someone worth reading about.
Editor’s Note: This article has been rewritten from the original to correct factual errors. The original article incorrectly focused on replicating a climate without the use of sensors. This project does require sensors to compare actual greenhouse conditions to historic climate conditions calculated by the library. We apologize to [934Virginia] for this and thank them for writing in to point out the errors.
Images courtesy of Wikimedia Commons.
Of all the things you never would have guessed you’d need just ten years ago, a YouTube subscriber counter would probably rank highly. You would have guessed that the little hits of dopamine accompanying each tick upward of a number would be so addictive?
As it turns out, lots of people wanted to keep a running total of their online fans, and a bewilderingly varied ecosystem of subscriber counters has cropped up. All of them rely on the API that YouTube exposes for such purposes, which as [Brian Lough] points out is about to change and break every subscription counter ever made. In the YouTube sub counter space, [Brian] is both an enabler – he built an Arduino wrapper to fetch YT sub counts easily – and a serial builder of displays for other YouTubers. The video below shows a collection of his work, many based on RGB LED matrix display, like the one used in his Tetris-themed sub counter. They’re all well-built, nice to look at, and sadly, destined for obsolescence sometime in August when the API changes.
The details of the API changes were made public in April, and for the subs count it amounts to rounding the count and displaying large counts as, for instance, 510k as opposed to 510,023. We’re confident that [Brian] and other display builders will be able to salvage some of their counters with code changes, but others will probably require hardware changes. Thanks, YouTube.
Continue reading “A Farewell To YouTube Sub Counters Set To Break With API Change”
Miniaturization has made smart watches possible, even for the DIY maker to tinker with. For those just getting to grips with basic digital electronics, it can be daunting, however. For those just starting out, [陳亮] put together a handy guide to building the core of an Arduino-based watch.
The writeup starts at the beginning, going over the basic hardware requirements for a smart watch. This involves considering size, packaging and power draw, as well as the user interface. The build settles on an Arduino Pro Micro, as it uses the ATmega32U4 which eliminates secondary USB-to-serial chips, helping cut down on power consumption. A square IPS LCD display is used to display an analog-style watch face, and time is kept by a DS3231 real-time clock. A pair of small vibration sensors are used to wake the watch when the user moves their wrist to check the time.
While it doesn’t cover the final assembly into a watch-like form factor, it’s a handy guide on what it takes to build a working watch for those who are still getting their feet wet with hardware. Once you’ve got that down, it’s time to contemplate how you’ll build the sleek exterior. Naturally, a good maker has that covered, too.
There’s something seriously wrong with the Arduino walkie-talkie that [GreatScott!] built.
The idea is simple: build a wireless intercom so a group of motor scooter riders can talk in real-time. Yes, such products exist commercially, but that’s no fun at all. With a little ingenuity and a well-stocked parts bin, such a device should be easy to build on the cheap, right?
Apparently not. [GreatScott!] went with an Arduino-based design, partly due to familiarity with the microcontroller but also because it made the RF part of the project seemingly easier due to cheap and easily available nRF24 2.4 GHz audio streaming modules. Everything seems straightforward enough on the breadboard – an op-amp to boost the signal from the condenser mic, a somewhat low but presumably usable 16 kHz sampling rate for the ADC. The radio modules linked up, but the audio quality was heavily distorted.
[GreatScott!] assumed that the rat’s nest of jumpers on the breadboard was to blame, so he jumped right to a PCB build. It’s a logical step, but it seems like it might be where he went wrong, because the PCB version was even worse. We’d perhaps have isolated the issue with the breadboard circuit first; did the distortion come from the audio stage? Or perhaps did the digitization inject some distortion? Or could the distortion be coming from the RF stage? We’d want to answer a few questions like that before jumping to a final design.
We love that [GreatScott!] has no issue with posting his failures – we’ve covered his suboptimal CPU handwarmer, and his 3D-printed BLDC motor stator was a flop too. It’s always nice to post mortem these things to avoid a similar fate.
Continue reading “Fail Of The Week: The Arduino Walkie That Won’t Talkie”