RealTimeClock inaccurate

I got a Uno R4 wifi hoping to use it as a wireless datalogger... tracking the state of the digital inputs with a timestamp.
It appears to me that the RTC is so inaccurate that it is not going to be useful
I just read the topic "Can we fix the RTC?" there didn't seem to be a fix at that point.
Has there been any fixes since that thread?

I would be interested in connecting some sort of RTC on a chip to the R4, but I haven't been able to find anything that specifically shows how to do that... I really am not interested in any programming to try to make up for the clock's accuracy.
thank you
Realolman

Can you connect your data logger to the Internet ?

The DS3231 modules typically keep time accurate to around +/- 1 minute per year.

1 Like

No.
This is because the Uno R4 has a free running clock so you can't fix it as it stands.

However, you can get other boards based on the same processor that has crystals fitted to get round this problem.

See.

I used THIS one ... it has both the quartz for the main MCU clock and the quartz for the RTC at a very affordable cost. I loaded the Arduino UNO R4 MINIMA bootloader onto it and, with just a few instructions, activated the two clocks with their respective crystals. :wink:

It is also quite easy to write a 'variant' to use all the pins it provides.

Guglielmo

1 Like

I'm disappointed to see that there is no fix... It's not like I spent much money on it, but not being able to keep reasonably accurate time on a microprocessor is not something I saw coming... I could get NTP time I guess, but I didn't want to.

I bought it strictly for the wifi. I'd a traded the LED matrix for RTC.

Thank you all for your posts
Realolman

@realolman:

If you search here on the forum, this topic has been discussed many times and some solutions have been proposed to improve the accuracy.

Try reading HERE.

Guglielmo

Thank you for your reply
I read this before i posted.

Realolman

Unfortunately, there are no other solutions without quartz ... :roll_eyes:

Guglielmo