Hm I used purge command. And i dont have file /etc/fake-hwclock.data I am using latest Raspbian edition,stretch. Tomorrow we are going on location, so for now will need to work like this ;) In the meantime, i hope to arrange something. Internet on location is ok, so everything should work fine except this problem. Or even if there was workaround to skip first console time update, that would solve my problem, because console is not so bad at timekeeping, its important that its within few minutes, few seconds doesnt matter. Regards
On Saturday, January 20, 2018 at 8:21:45 PM UTC+1, Tom Keffer wrote: > > Incidentally, before you purge the fake clock, see if the file > /etc/fake-hwclock.data is still around. That would cause your symptoms. > Purging should remove the file. If it's not, remove it manually: > > sudo rm /etc/fake-hwclock.data > > > -tk > > > On Sat, Jan 20, 2018 at 12:12 PM, Thomas Keffer <[email protected] > <javascript:>> wrote: > >> If you removed the fake clock, it should start at unix epoch time zero. >> If it's not, it's because the module was not removed properly. See the >> Wiki >> <https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock> >> . >> >> In any case, the running an RTC is the right thing to do, particularly >> with a remote location that may have intermittent, or very delayed, access >> to NTP. >> >> -tk >> >> On Sat, Jan 20, 2018 at 11:59 AM, mwall <[email protected] >> <javascript:>> wrote: >> >>> weewx will not process data until the time is after 00:00:00 01jan2000 >>> utc. so perhaps your pi is reverting/starting at a time that is later than >>> that. >>> >>> you can make the weewx time check a bit more robust by modifying >>> engine.py >>> >>> change this: >>> >>> while weewx.launchtime_ts < 946684800: >>> >>> to a more recent value. however, that approach can only go so far. >>> >>> the init systems also have mechanisms for delaying the start of weewx. >>> unfortunately, those may not do exactly what you expect. for example, you >>> might make weewx start after ntp, but just because ntp has started, the >>> system may not have a valid time. you'll have to dig deeper to tell your >>> init system that weewx should not start until after ntp has started AND >>> after ntp has set the system time. >>> >>> or put a real-time clock on the pi. >>> >>> m >>> >>> -- >>> 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] <javascript:>. >>> For more options, visit 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.
