Recently got my DS3231 and have questions to ask...

BlowbubblesBlowbubbles Posts: 5Member
in HARDWARE & SYSTEM
Hi there,

I recently got my DS3231 module labeled ZS-042 off from http://www.kynix.com/Detail/99971/DS3231.html and it came with a CR2032 3V battery.

The module works at 3.3V and also 5V however after some days of usage at 5V I noticed that the battery has become quite "thick". A quick check with the multimeter confirms that the module force-charges the battery with VCC! Not quite nice.
Here a pic:


So you should at least power this module only at 3.3V, even then, question to the experts:
is it save to "charge" a 3V CR2032 at 3.3V continuously without it breaking after some time?
2nd question: is it ok to charge a LIR2032 at 5V?

Other than that the module works quite well with the time library.

Best regards!

Comments

  • PedalToTheMetalPedalToTheMetal Posts: 57Member
    Wrong forum, should be in the off-topic section instead.
    Anyway. The most 2032 cells are not chargeable, so desolder the trickle charger circuit (I googled the schematic and there is a 200 Ohm resistor and some random diode, desolder one or both). Also keep in mind any non-chargeable cell if cracked may actually burn up, and there is always a warning text stating that ;) A fun idea is to swap out the resistor with something in 1-2k range and replace the battery with a supercapacitor, which may or may not suit your needs. And I truly hope you aren't using Arduinos as they are probably the worst way to mess-up an AVR chip I ever seen :)
  • BlowbubblesBlowbubbles Posts: 5Member
    Sorry and thanks for your response :p :p

    Ah, ic, I think it would be best to use a supercap instead of the CR/LIR battery, something like this:



    How about that？

    Actually, I wanted to use the ds3231 to send an interrupt every second to my arduino pro mini (5V). There are some libs that set up the ds3231 to do just that however not the most cited one maybe. :|
  • PedalToTheMetalPedalToTheMetal Posts: 57Member
    Under the "worst way" I actually meant not rigging the RTC, but using the Aurduinos (not the stock AVRs!) themselves as using a device that comes with a lot of unnecessary code itself and gets even more of it from untested compilers and libs is actually not the best choice for sure ;) Anyway, neither the battery or a cap is needed if you simply want to use the chip as a TCXO, no libs either as it basically needs just a couple of writes (pretty easy on stock AVRs in ASM code, can't tell if it remains the same for arduinos) - though I prefer SPI for one's speed and the lack of need in a TWI statemachine which is pretty fat compared to the SPI sender code (the latter is usually around only 10 instructions), also you can do an SPI send-receive in a direct call, without interrupts and software state flags you'll need to keep the TWI dataflow from stalling the chip (it is not always essential yet is not really nice, especially for the real-time applications with microseconds accuracy).
  • BlowbubblesBlowbubbles Posts: 5Member
    Guess figure out what you mean, nice and awesome response, a huge thanks for your sharing, you know, your knowledge and experience my friend :)
    Have a nice day!
Sign In or Register to comment.