DS1302 Real-Time Clock (RTC) Module with CR2032 Battery Backup, 3.3V/5V Compatible for Arduino MCU

DS1302  Clock Module Product Overview

The DS1302 real-time clock module is a high‑precision RTC module based on the DALLAS DS1302 trickle‑charge clock chip. It communicates with microcontrollers via a simple 3‑wire serial interface, providing complete calendar information including seconds, minutes, hours, day, week, month, and year with automatic leap‑year compensation valid until 2100. The module features an onboard 32.768KHz crystal and a CR2032 coin cell battery (on the battery‑included version). When the main power supply is disconnected, the module automatically switches to battery power, ensuring continuous timekeeping for years. The module operates on both 3.3V and 5V systems, making it compatible with Arduino, STM32, 8051, and other mainstream microcontroller platforms. It is widely used in digital clocks, data logging, timing control, smart home applications, and any scenario requiring precise timekeeping.

DS1302  Clock Module Core Features

The DS1302 RTC chip integrates a real‑time clock/calendar and 31 bytes of non‑volatile static RAM, communicating with the host MCU via a 3‑wire serial interface (CE, I/O, SCLK). The clock counts seconds, minutes, hours, days, weeks, months, and years, automatically adjusts for month lengths (including months with fewer than 31 days), and features leap‑year correction. It supports both 24‑hour and 12‑hour (with AM/PM) formats.

The module features a single‑sided PCB design measuring 44mm × 23mm × 1.6mm with four 3.1mm mounting holes for secure installation. The 32.768KHz crystal is imported from Japan with a 6pF matching capacitor. The DS1302 chip comes in an 8‑pin DIP package and is mounted on an IC socket for easy replacement.

DS1302  Clock Module Power Supply & Battery Backup

The module operates on 3.3V or 5V and can be directly connected to both 5V and 3.3V microcontrollers. The chip supply voltage ranges from 2.0V to 5.5V, with the same range for the backup battery. At 2.0V, the quiescent current is less than 300nA, ensuring long battery life.

The backup battery is a genuine Tianqiu CR2032, rated at 3V with 260mAh capacity (non‑rechargeable). Theoretical data retention exceeds 10 years.

DS1302  Clock Module Pin Definitions

VCC：Main power positive (3.3V or 5V)

GND：Power ground

CLK (SCLK)：Serial clock input

DAT (I/O)：Serial data input/output

RST (CE)：Reset / chip select

DS1302  Clock Module Applications

Digital clocks and calendars

Data logging with timestamps

Timing control (timer switches, smart irrigation, automatic feeders, etc.)

Smart home applications (smart alarms, timed lighting, security system time sync)

Industrial control (equipment operation logs, production timing)

Education and experiments (MCU learning, RTC principle teaching)

Key Advantages

The DS1302 clock module delivers precise real‑time timekeeping at extremely low cost with a simple interface. The onboard CR2032 battery ensures continuous timekeeping for years after main power loss, with a monthly drift of less than 1 minute. The 3‑wire serial interface uses only 3 MCU I/O pins, conserving valuable resources. The module is compatible with both 3.3V and 5V systems, directly connecting to Arduino, STM32, 8051, and other popular microcontrollers. The IC socket allows for easy chip replacement. Mature Arduino library support and abundant open‑source examples enable rapid development, making it a reliable and economical RTC solution for electronics projects and embedded development.

Why Choose QIXINWEI

Years of experience in the electronics industry. Trusted by global customers.

Massive In-Stock Inventory – Ready to ship promptly

BOM Matching Service – One-stop solution, save time

PCBA Customization – Professional engineering team creates tailor-made solutions based on your needs

Cost-Effective & Efficient – Better channel, better cost

A dedicated team makes your procurement smoother.

Contact us for BOM quotes or PCBA inquiries

FAQ

1. What is the difference between the DS1302 and the DS3231 as RTC modules? How do I choose?
The DS1302 is an entry‑level RTC that communicates over a simple 3‑wire SPI interface at low cost, suitable for general timing and calendar applications where accuracy requirements are moderate. The DS3231 has a built‑in temperature‑compensated crystal oscillator (TCXO) achieving ±2 ppm accuracy (about 1 minute per year), while the DS1302 relies on an external 32.768 kHz crystal whose accuracy is influenced by crystal quality and ambient temperature, typically drifting 1–2 minutes per month. If your project is cost‑sensitive and periodic time correction is acceptable, the DS1302 works well; for high precision or hard‑to‑maintain devices, the DS3231 is the better choice.

2. How long does the CR2032 battery on the module last? Does the clock keep running after power loss?
The CR2032 battery (typically 200–240 mAh) powers the chip solely for maintaining timekeeping and retaining internal RAM when the main supply is absent. The DS1302 draws less than 300 nA in backup mode, so theoretically it can last several years; accounting for battery self‑discharge, reliable backup is usually 1–3 years. When the module is powered by the 3.3V or 5V main supply, the DS1302 runs entirely from the main supply and the battery is not drained. Note that CR2032 cells are non‑rechargeable; never connect the module directly to a charging circuit, as this poses a risk of leakage or explosion.

3. The DS1302 has 31 bytes of internal RAM. What is it for, and what data can I store?
This 31‑byte battery‑backed RAM is a distinctive feature of the DS1302. It is independent of the clock registers and remains preserved by the backup battery after main power is removed. You can use it to store small amounts of data that must survive power cycles, such as device configuration parameters, user settings, last operating state, or checksums—no external EEPROM chip required. It is ideal for low‑power embedded devices that occasionally need to record small pieces of information.

4. What is the DS1302’s 3‑wire interface, and how do I connect it to an MCU?
The 3‑wire interface consists of CE (chip enable), I/O (bidirectional data), and SCLK (clock). Simply connect these three signal lines to any GPIO pins on your MCU, and then connect VCC and GND to the power supply. Software communication is done by bit‑banging the protocol or using existing Arduino/STM32 library functions that handle the timing. Compared to an I²C interface, it does not occupy a dedicated hardware peripheral and offers more flexible pin selection, but communication speed is slower and strict timing control is required.

5. The module supports both 3.3V and 5V systems. How should I power it safely?
The module’s VCC should be connected to your MCU’s supply voltage. If the system is 3.3V, connect VCC to 3.3V; if it is 5V, connect VCC to 5V. The DS1302 has a wide operating voltage range (approximately 2.0V–5.5V) and the data pins’ logic levels automatically track VCC, so no external level‑shifting ICs are needed when interfacing with either 3.3V or 5V MCUs. Just ensure VCC matches the MCU supply voltage.

6. What should I do when using the module for the first time? How do I set the current time?
A new module typically does not have a valid time pre‑set at the factory. You need to write the current date and time once through your program. Using the Arduino IDE or STM32CubeIDE, call the time‑setting function in the DS1302 library (e.g., `rtc.setDateTime()`) to write the compile‑time or a manually defined time into the chip. Once written successfully, the chip begins counting automatically. After that, you only need to check whether calibration is required after replacing the battery or upon power‑up.

7. Why does the time I read appear as garbage or all 0xFF?
This is usually caused by one of the following: ① Incorrect communication timing—the DS1302 has strict requirements for clock edges and data setup/hold times; if the MCU frequency is too high or the code lacks appropriate delays, read/write operations may fail. ② Low or poorly connected battery—insufficient backup battery voltage can cause the clock registers to lose their contents, requiring re‑initialization after power‑up. ③ Oscillator failure—a poorly soldered or damaged external 32.768 kHz crystal can halt the oscillator. Checking the battery, solder joints, and timing is the most effective troubleshooting approach.

8. Can the DS1302 generate an interrupt signal? How can I wake up the MCU on a schedule?
The DS1302 does not have a dedicated interrupt output pin. If you need a scheduled wake‑up function, your software must periodically poll the DS1302’s time registers through the CE/I/O/SCLK interface and trigger the desired action when the preset time is reached. For systems that require a hardware interrupt, consider upgrading to an RTC chip with a programmable square‑wave output (such as the DS3231’s SQW pin) or a dedicated alarm interrupt pin.

9. How accurate is the crystal on the module? How can I improve timekeeping accuracy?
The DS1302 relies on an external 32.768 kHz crystal with a typical accuracy of about ±20 ppm, resulting in a monthly drift of 1–2 minutes. To improve long‑term accuracy you can: ① choose a higher‑quality crystal with better load‑capacitance matching; ② place the crystal as close as possible to the chip pins on the PCB and away from heat sources and interference; ③ implement periodic software time correction—for example, via WiFi, GPS, or manual adjustment at regular intervals. If high precision is essential, choose a DS3231 module with a built‑in TCXO.

10. Can this DS1302 RTC module be used with STM32, ESP32, or Raspberry Pi? Is the driver code portable?
Yes. The DS1302 uses a 3‑wire SPI protocol that is independent of the MCU type; you only need to implement the corresponding GPIO read/write and timing control on the target platform. Mature third‑party libraries exist for Arduino (e.g., `DS1302` or `RTCx`), and the same C/C++ code can be used on STM32 and ESP32 by adapting the GPIO functions. Raspberry Pi can drive it through WiringPi or pigpio libraries. The driver itself is not complex—at its core it involves only a few dozen lines of I/O operations.