Time, RTC & Clocks

The display is one of the most important design elements of any clock. It determines readability, power consumption, aesthetics and overall user experience. There are several common display technologies used in clock projects, each with its own strengths and limitations. This guide compares the most popular options: 7-segment displays, LCDs, OLEDs and ePaper. 7-Segment Displays […]

The DS3231 is one of the most accurate and widely used real-time clock (RTC) ICs available for embedded systems. Unlike simpler RTCs such as the DS1307, the DS3231 includes an integrated crystal and temperature compensation, making it a reliable choice for applications that require stable and precise timekeeping. For most modern designs, the DS3231 has

Handling time zones and daylight saving time (DST) is one of the most common sources of errors in embedded systems. While obtaining accurate time is relatively straightforward using RTCs, GPS or NTP, converting that time into meaningful local time is often more complex than expected. This article explains how to correctly handle UTC, time zones

The DS1307 and DS3231 are two of the most commonly used real-time clock (RTC) ICs in Arduino and embedded projects. While they are similar in function and even share the same I2C address, their performance and internal design are very different. This article compares both RTCs and helps you decide which one is the better

Handling time in embedded systems is not only about keeping accurate time, but also about storing, transmitting and processing it efficiently. One of the most widely used representations is Unix time, also known as epoch time. This article explains Unix time, common time formats and how they are used in embedded systems. What Is Unix

Real-time clocks (RTCs) are designed to keep time continuously, even when the main system power is removed. This is made possible by a backup power source, typically a coin cell battery or, in some designs, a supercapacitor. Choosing the right backup method is critical for reliable long-term timekeeping. Why RTC Backup Power Is Needed When

In professional and robust embedded systems, relying on a single time source is often not sufficient. Each method—RTC, GPS, NTP and atomic clock receivers—has strengths and weaknesses. By combining multiple time sources, you can build systems that are both highly accurate and reliable under all conditions. Why Combine Time Sources? No single method is perfect

Most real-time clock (RTC) modules such as the DS1307 and DS3231 use the I2C bus for communication. While I2C is simple and widely supported, many practical issues arise from incorrect wiring, missing pull-up resistors or bus conflicts. This guide explains how to connect RTC modules correctly and troubleshoot common problems. Basic I2C Wiring I2C uses

Even high-quality real-time clocks (RTCs) such as the DS3231 are not perfectly accurate. Over time, small frequency errors accumulate and cause measurable drift. In applications where higher precision is required, software-based calibration can significantly improve accuracy. This article explains how drift occurs and how to correct it using calibration techniques. What Is Clock Drift? Clock

Atomic clock receivers allow electronic systems to synchronize automatically with highly accurate national time standards. These systems use long-wave radio signals transmitted at around 60 kHz and are widely used in radio-controlled clocks and precision timing devices. This article explains how these signals work and how they are used in embedded systems. What Are 60