The problem with not having an RTC is mostly around startup, when the system time has not yet been set by NTP. Starting weewx can be delayed until the system time is set, but that becomes problematic if the internet connection isn’t available or is delayed when the system boots. Not having an RTC also makes things like boot-time log analysis more difficult since the system clock doesn’t get set until much later. It can work, especially if you have a very reliable internet connection, but is more brittle. Once it’s running, NTP is plenty accurate, better than the RTC in fact. Unless you need those GPIO pins for something else, five bucks for an RTC module is a good investment, IMHO.
-Les > On 12 Mar 2017, at 13:38, Francisco Puig <[email protected]> wrote: > > Anyone here is using an RTC (hardware) on a raspberry pi ? I'm trying to find > data of if this is really necessary for the reports accuracy even when the pi > is connected to the internet using the raspbian pre-configured NTP. > > > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
