alexan_e
Administrator
I guess it depends on the library functions you use, in AVR I have a library that uses tw_write(1); for write with acknowledge and tw_write(0); for write with Nak so there is no need for separate ack/nak
Maybe your functions already use acknowledge , I don't know.
If it is incrementing to 25,26,27 then you are not reading the correct value,I don't see how the hour becomes higher than 23.
The strange part is that it works fine in proteus and I can't explain that, this seems to imply that there is a hardware problem.
Is your i2c operating in a proper frequency , maybe you can try with a lower clock to see if it helps.
You said the but resistors are in place and the battery pin is grounded (?)
How exactly do you read these 25..26 values?
what setting do you apply to hour so that you can get that?
Do you set it to 23:59 and wait to increment and you see 24:00?
Maybe your functions already use acknowledge , I don't know.
If it is incrementing to 25,26,27 then you are not reading the correct value,I don't see how the hour becomes higher than 23.
The strange part is that it works fine in proteus and I can't explain that, this seems to imply that there is a hardware problem.
Is your i2c operating in a proper frequency , maybe you can try with a lower clock to see if it helps.
You said the but resistors are in place and the battery pin is grounded (?)
How exactly do you read these 25..26 values?
what setting do you apply to hour so that you can get that?
Do you set it to 23:59 and wait to increment and you see 24:00?