You have to be pretty ambitious to modify a clock to run for 50 years on a single battery. You also should probably be pretty young if you think you’re going to verify your power estimates, at least in person. According to [Josh EJ], this modified quartz analog clock, which ticks off the date rather than the time, is one of those “The March of Time” projects that’s intended to terrify incentivize you by showing how much of the year is left.
Making a regular clock movement slow down so that what normally takes an hour takes a month without making any mechanical changes requires some clever hacks. [Josh] decided to use an Arduino to send digital pulses to the quartz movement to advance the minute hand, rather than let it run free. Two pulses a day would be perfect for making a 30-day month fit into a 60-minute hour, but that only works for four months out of the year. [Josh]’s solution was to mark the first 28 even-numbered minutes, cram 29, 30, and 31 into the last four minutes of the hour, and sort the details out in code.
As for the low-power mods, there’s some cool wizardry involved with that, like flashing the Arduino Pro Mini with a new bootloader that reduces the clock speed to 1 MHz. This allows the microcontroller and RTC module to run from the clock movement’s 1.5 V AA battery. [Josh] estimates a current draw of about 6 μA per day, which works out to about 50 years from a single cell. That’s to be taken with a huge grain of salt, of course, but we expect the battery will last a long, long time.
[Josh] built this clock as part of the Low-Power Challenge contest, which wrapped up this week. We’re looking forward to the results of the contest — good luck to all the entrants!
We see a lot of clocks here at Hackaday, so many now that it’s hard to surprise us. After all, there are only so many ways to divide the day into intervals, as well as a finite supply of geeky and quirky ways to display the results, right?
That’s why this periodic table clock really caught our eye. [gocivici]’s idea is a simple one: light up three different elements with three different colors for hours, minutes, and seconds, and read off the time using the atomic number of the elements. So, if it’s 13:03:23, that would light up aluminum in blue, lithium in green, and vanadium in red. The periodic table was designed in Adobe Illustrator and UV printed on a sheet of translucent plastic by an advertising company that specializes in such things, but we’d imagine other methods could be used. The display is backed by light guides and a baseplate to hold the WS2812D addressable LEDs, and a DS1307 RTC module gives the Arduino Nano a sense of time. The 3D printed frame of the clock has buttons for setting the time and controlling the clock; the brief video below shows it going through its paces.
We really like the attention to detail [gocivici] showed here; that UV printing really gave some great results. And what’s not to like about the geekiness of this clock? Sure, it may not be as action-packed as a game of periodic table Battleship, but it would make a great conversation starter.
It might seem antiquated, but Morse code still has a number of advantages compared to other modes of communication, especially over radio waves. It’s low bandwidth compared to voice or even text, and can be discerned against background noise even at extremely low signal strengths. Not every regulatory agency requires amateur operators to learn Morse any more, but for those that do it can be a challenge, so [Cristiano Monteiro] built this clock to help get some practice.
The project is based around his favorite microcontroller, the PIC16F1827, and uses a DS1307 to keep track of time. A single RGB LED at the top of the project enclosure flashes the codes for hours in blue and minutes in red at the beginning of every minute, and in between flashes green for each second.
Another design goal of this build was to have it operate with as little power as possible, so with a TP4056 control board, single lithium 18650 battery, and some code optimization, [Cristiano] believes he can get around 60 days of operation between charges.
For a project to help an aspiring radio operator learn Morse, a simple build like this can go a long way. For anyone else looking to build something similar we’d note that the DS1307 has a tendency to drift fairly quickly, and something like a DS3231 or even this similar Morse code clock which uses NTP would go a long way to keeping more accurate time.
As [Phil Greenland] explains in the first part of his excellent write-up, the lithium battery used to keep the real-time clock (RTC) going on the Macintosh SE/30 has a nasty habit of exploding and leaking its corrosive innards all over the board. Looking to both repair the damage on a system that’s already had a battery popped and avoid the issue altogether on pristine boards, he started researching how he could replace the battery with something a bit more modern.
It turns out, the ATtiny85 is pin-compatible with the Mac’s original RTC chip, and indeed, [Andrew Makousky] had already written some code that would allow the microcontroller to emulate it. This is actually a bit more complex than you might realize, as the original RTC chip was doing double-duty: it also held 256 bytes of parameter random access memory (PRAM), which is where the machine stored assorted bits of info like which drive to boot from and the mouse cursor speed.
[Dmytro Panin] lives in Kyiv, Ukraine where there have been rolling blackouts to stabilize the power grid. To help keep track of when the blackouts might happen, be they planned or emergency, and to get more information on how long the blackouts last, [Dmytro] has created a blackout logger.
The build consists of a Raspberry Pi Pico that connects to a DS3231 real time clock (RTC) with a Waveshare 3.7 inch eInk display which [Dmytro] puts into a custom 3D printed case. The RTC has it’s own small power supply, often times from a coin cell battery attached to the module, allowing it to keep time when the module and other devices attached to it are powered off.
The Raspberry Pi Pico is programmed to “poll” every 30 seconds, writing the current time to a file. Should the unit lose power, the last time, within a 30 second window, is available when power is restored and the unit wakes up again. Since the RTC has kept the current time, there is enough information to display the duration of the blackout. The eInk screen ensures that the information is readily available, even when there is no power.
War is not the only reason blackouts can occur and we’ve covered some issues with blackouts in Texas and California in the US.
[Marek] has an impressive collection of old Soviet-style Geiger counters. These are handy tools to have in some specific situations, but for most of us they would be curiosities. Even so, they need some help from the modern world to work well, and [Marek] has come up with some pretty creative ways of bringing them into the 21st century. This version, for example, adds WiFi capabilities.
This build is based on the STS-5 Geiger tube but the real heavy lifting is handled by an ESP8266 which also provides a wireless network connection. There are some limitations to using an ESP8266 to control a time-sensitive device like a Geiger tube, especially the lack of local storage, but [Marek] solves this problem by including a real-time clock and locally caching data until a network connection is re-established. Future plans for the device include adding temperature and atmospheric temperature sensors.
Eventually this Geiger counter will be installed in a watertight enclosure outside so [Marek] can keep an eye on the background radiation of his neighborhood. Previously he was doing this with another build, but that one only had access to the network over an Ethernet cable, so this one is quite an upgrade.
Most of the design and engineering required to improve the efficiency of the data logger involve standard practices for low-power devices such as shutting off unnecessary components and putting the device to sleep when not actively running, but this build goes far beyond that. The Vcc pin on the RTC was clipped which disables some of its internal logic but still keeps its basic functionality intact.
All of the voltage regulators were removed or disabled in favor of custom circuitry that doesn’t waste as much energy. The status and power LEDs were removed where possible, and the entire data logger is equipped with custom energy-efficient code as well.
If you’re starting a low-power project, even one that isn’t a datalogger, it’s worth checking out this build to see just how far you can go if you’re willing to hack at a PCB with cutting tools and a soldering iron. As to why this data logger needed such a low power requirement, it turns out it’s part of a kit being used in classrooms and using a coin cell brought the price of the entire unit down tremendously. Even if you have lithium cells on hand, though, it’s still worthwhile to check out the low power modes of your microcontroller.