I understand this, but after power on, RPI (stretch) clock is on latest time while it was on, no matter i have purged fake clock. I tried DietPi OS, without any addon, and it is the same again. RPI is now working on 1630m ASL, so I will not test on it now, for now I update it manually every now and then. I have another test RPI at home(DietPi running with Davis Vantage Pro2 connected) so when I have time, I will try your ideas. On this one, setup is default, and internet was down for 30 minutes, and while changing router RPI was restarted, and now i have again wrong time on console(test setup at home) Is there possible that strech has some other type of clock(not fake clock)? Maybe I should install older version of Raspbian? Or there is some other way.
Best regards Ċ½eljko from Croatia On Sunday, January 21, 2018 at 7:24:23 PM UTC+1, Andrew Milner wrote: > > What does the log show when you start up after a power outage?? > > The rp should have time set to epoch 0 - jan 1970 or whatever following > the power outage - assuming that all references to fake hardware clock have > been correctly removed/purged > > weewx will start, but should detect the time is not > 2000 and so wait for > a better time - which will not happen until after NTP has set the rpi time > > once time is set > 2000 weewx should then start to process the data and > sart by retrieving logged data from the davis > > weewx should then start the main packet loop > > > > On Sunday, 21 January 2018 19:25:38 UTC+2, Zeky91 wrote: > >> 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 <tke...@gmail.com> >>> 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 <mw...@users.sourceforge.net> >>>> 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 weewx-user+...@googlegroups.com. >>>>> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
