Chronodot 2.1
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- adafruit_support_rick
- Posts: 35092
- Joined: Tue Mar 15, 2011 11:42 am
Re: Chronodot 2.1
But are you using a chronodot with the logger shield?
-
- Posts: 15
- Joined: Thu Jan 23, 2014 4:05 pm
Re: Chronodot 2.1
Yes, I do. The chronodot is mounted ( intagrated) on the Datalogger.
- adafruit_support_rick
- Posts: 35092
- Joined: Tue Mar 15, 2011 11:42 am
Re: Chronodot 2.1
That won't work. The Chronodot and the DS1307 have the same I2C address, and therefore can't share the same bus. You will have to remove the DS1307 from the datalogger
- tanery
- Posts: 7
- Joined: Mon Dec 02, 2013 10:08 pm
Re: Chronodot 2.1
Re: Chronodot 2.1
Post by i_can » 05 Feb 2014 22:19
The question was why the RTC cannot be synchronize?
// following line sets the RTC to the date & time this sketch was compiled
// uncomment it & upload to set the time, date and start run the RTC!
RTC.adjust(DateTime(__DATE__, __TIME__));
But i still see the serial monitor printing:
2165/165/165 165:165:85
since 1970 = 1396827985s = 16166d
now + 7d + 30s: 2014/4/13 23:46:55
and you guessed, that RTC was damaged.
So
adafruit_support_rick wrote:
It's possible that the RTC is damaged, then. All I can do at this point is to replace the datalogger. Please email [email protected] with a link to this thread.
I think its not damaged.
[/quote]
im having the same problem but i dont have the data logger i just have the Chronodot 2.1
- tanery
- Posts: 7
- Joined: Mon Dec 02, 2013 10:08 pm
Re: Chronodot 2.1
fix for the
2165/12/31 23:60:60 since midnight 1/1/1970 = 1890322364s = 21878d now +7d +30s: 2029/12/2 17:33:14
this just repeats on and on and on nothing changes
using the example for ds1307
replace all ref to ds1307 with ds3231
and remove the if statement and that fixes it woot
2165/12/31 23:60:60 since midnight 1/1/1970 = 1890322364s = 21878d now +7d +30s: 2029/12/2 17:33:14
this just repeats on and on and on nothing changes
using the example for ds1307
replace all ref to ds1307 with ds3231
and remove the if statement and that fixes it woot
- gmglickman
- Posts: 39
- Joined: Wed Oct 08, 2008 10:53 pm
Re: Chronodot 2.1
While generally considered a drop-in replacement for the DS1307, the DS3231 (as in the Cronodot) differs in how the oscillator control and status flags are handled.
In configuring the DS1307 RTC, bit7 of register 0 is the CH or clock halt bit and should be set to zero to start the on-board oscillator. On the DS3231, however, the oscillator stop flag (OSF) is moved to bit7 of register 0F (hex.) In either case, 0=running, 1=not running.
If the DS1307 library looks to CH bit 7 of register 0 for oscillator status in the statement "if (! RTC.isrunning())," then that statement will always return true on the DS3231, where that bit is part of the seconds register and always reads 0. Hence the DS3231 will not be set to the compiled time as expected.
In configuring the DS1307 RTC, bit7 of register 0 is the CH or clock halt bit and should be set to zero to start the on-board oscillator. On the DS3231, however, the oscillator stop flag (OSF) is moved to bit7 of register 0F (hex.) In either case, 0=running, 1=not running.
If the DS1307 library looks to CH bit 7 of register 0 for oscillator status in the statement "if (! RTC.isrunning())," then that statement will always return true on the DS3231, where that bit is part of the seconds register and always reads 0. Hence the DS3231 will not be set to the compiled time as expected.
Please be positive and constructive with your questions and comments.