|Package Dimensions||11.43 x 8.38 x 2.79 cm; 23 Grams|
|Item Model Number||3-01-0435|
|Is Discontinued By Manufacturer||No|
|Manufacturer Part Number||3-01-0435|
|Item Weight||23 g|
HiLetgo 5pcs DS3231 AT24C32 Clock Module Real Time Clock Module IIC RTC Module for Arduino Without Battery
|Price:||+ $7.50 Delivery|
Enhance your purchase
- HiLetgo DS3231 AT24C32 Clock Module Real Time Clock Module
- Working voltage : 3.3 -. 5 .5 V
- Clock chip: high-precision clock chip DS3231M
- Memory chips:. AT24C32
Buy it with
Frequently bought together
Have a question?
Find answers in product info, Q&As, reviews
Your question might be answered by sellers, manufacturers, or customers who bought this product.
Please make sure that you've entered a valid question. You can edit your question or post anyway.
Please enter a question.
DS3231 AT24C32 Clock Module Real Time Clock Module IIC RTC Module for Arduino
1. Dimension: 38mm* 22mm * 14mm
2. Weight:. 8g
3. Working voltage : 3.3 -. 5 .5 V
4. Clock chip: high-precision clock chip DS3231
5. Clock accuracy within range :0-40 ¡æ, accuracy 2ppm, about 1 minute in error
6. Programmable square-wave output
7. Real-time clock, it can generate seconds, minutes, hours, day, date, month and year, and provide time until 2100, and with leap year compensation.
8. Internal chip temperature sensor comes with an accuracy of ¡À 3 ¡æ
9. Memory chips:. AT24C32 (storage capacity of 32K)
10. IIC bus interface, the maximum transmission speed of 400KHz (working voltage of 5V)
11. IIC other devices can be cascaded, 24C32 address can be modified by a short circuit A0/A1/A2, the default address is 0x57
Review this product
Top reviews from other countries
For example in the product description:
"5. Clock accuracy within range :0-40, accuracy 2ppm, about 1 minute in error"
"6. Programmable square-wave output "
These are true for the SN version but not for the M variant which is accurate to 5ppm and has a fixed SQW output of 1hz
Come on guys if you are going to send out the MEMS version alter the specs to match.
Hookup is EASY - i2c is a simple protocol to use on any Arduino (just look up the pins on your model) and RTClib will connect and use the unit very easily.
The issue is keeping the time once set. I'd created several items that needed time over the last month so I've used several of these RTC units to keep time. However, after even a day there's a very big drift in time - several minutes, at times several 10s of minutes! This means there's really no point to that huge battery - the unit would do better using network time that would be adjusted every so often during the day.
The last issue is power consumption. It's HUGE - a large power led shines and wastes mAs galore when running. Of course if you're just starting out, the LED may be helpful to see things are turned on, but as I've had to build little project boxes for my things, I find this unit too large and too power-hungry, on top of not being able to keep time. So for practical time use, I'm looking at the Nano33 IoT which has RTC built in and other solutions where power consumption is low and size even so.
My main problem with it has to do with the design relating to the battery. First of all, the battery holder is very cheap and if you insert the battery and press down, it will not make contact. You have to just slightly push it in, ever so gently, and it has to sit in just the right spot to work.
Second, with this module as it ships, you CANNOT USE CR2032 BATTERIES. I say this because it tries to charge the batteries from VCC, and CR2032s are not rechargeable. It will slowly kill the battery, even when the battery is not in use. So you think, sure, just use an ML2032 rechargeable, right? NO, because it charges from a voltage just below VCC (which could be 5V!). It tries to use a diode and resistor as a voltage dropper and current limiter, but diode voltage drop is current-dependent. It will NOT reliably drop the voltage to 3-3.3V, where it needs to be for an ML2032. ML2032 batteries will die and potentially vent/leak from charging from too high a voltage. Definitely do NOT use a LIR2032 either, as those need to be charged with a specific charging system as well.
So why do we need the battery to charge from VCC? We DON'T. If you are using this module as many people would, you usually have voltage on VCC. The battery should just be there to keep time when VCC is removed. In that respect, it could last years without charging. So, looking at the schematic, all you have to do is desolder the tiny 200ohm resistor, labeled "201" next to the main chip and the diode (right next to SCL). It will no longer draw extra current and thus kill whatever battery you have inserted, and the battery will still power the chip when VCC is removed. I also recommend desoldering the LED if you are powering your project with a battery system, since it gulps power.
Finally, IIRC the square wave output and possibly 32khz output are on by default. They use a ton of power. You have to disable them in your code to make this thing even remotely efficient.
After all these changes, it still uses over 100uA, but it's usable.
Now that I've desoldered multiple parts and carefully inserted my battery, it keeps time reasonably well and doesn't slowly destroy whatever battery I put in it. I'm almost tempted to desolder the crappy DS3231 and replace it with a genuine one, but at that point I might as well just be making my own module.