Not sure if this belongs in this forum, but it's my best guess...
I purchased one of your ChronoDot RTC modules.
How long should it operate on battery before the battery voltage drops below
the expected nominal voltage of 2.7v?
Is 2.7v a reasonable anticipated voltage level on the BAT pin as detected by
the Arduino Analog input?
I'm asking because I'm now on my second 1632 and it is now reporting 2.5v.
I'm measuring the voltage by connecting the BAT pin on the ChronoDot
directly to pin 15 on my Arduino Mega 2560.
The readout is based essentially on this (it's part of a much larger
application):
setup()
{
pinMode(15, INPUT);
digitalWrite(15, LOW);
}
loop()
{
int vlvl;
vlvl = analogRead(15);
Serial.print("Voltage: ");
Serial.print((float)(vlvl*5/1024));
}
Should I be using a lower discharge-detection battery value than 2.7v? Is
2.5v reasonable?
The Chronodot has probably had a total of ≤10 hours run time without Vcc
since installing this battery.
The previous battery also lasted about 10 hours of non-Vcc time before
dropping below 2.7v.
This seems like an awfully fast drain of a backup battery for an RTC.
Any thoughts/information greatly appreciated.
I wish you guys made a 1672-based clock. Then again, I wish Maxim made a
hyper-accurate module like the one ChronoDot is based on, but, in a 32-bit
counter instead of BCD. (My application is setting the clock from internet
when available, so, all time storage and manipulation is seconds-since-epoch
(midnight Jan. 1 1970, UTC) and only the display is in human-readable
time/date format. Having to convert the ChronoDot back and forth is a bit of
a pain.

