Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Sun, Nov 27, 2016 at 10:40 AM, Andrew Milner wrote: > .. or you could just say weewx does not support feather . and > leave feather users to do their own thing if doing software archive > record generation from loop packets does not solve the

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

.. or you could just say weewx does not support feather . and leave feather users to do their own thing if doing software archive record generation from loop packets does not solve the problem. On Sunday, 27 November 2016 20:35:22 UTC+2, Tom Keffer wrote: > I'm getting lost in

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I'm getting lost in where we are. Let me try another suggestion. If you do not or cannot implement GETTIME on the feather, how about writing a new driver that inherits from the old vantage driver, but overrides getTime() and setTime()? It would look something like this (NOT TESTED): *File

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I just found set_time(). It has somthing todo with option --set-time. Is this an option I can trigger via weewx.conf? Thanks, Gustl -- 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

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Sonntag, 27. November 2016 14:05:56 UTC+1 schrieb Tom Keffer: > > On Sun, Nov 27, 2016 at 3:53 AM, gustl319 > wrote: > >> I've done some code searching. Please tell me if I'm right: >> >>- on startup do_sync() is called >>- in do_sync() is a call to getTime() >>

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Sun, Nov 27, 2016 at 3:53 AM, gustl319 wrote: > I've done some code searching. Please tell me if I'm right: > >- on startup do_sync() is called >- in do_sync() is a call to getTime() >- getTime() returns the GETTIME answer >- if the difference to system

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I've done some code searching. Please tell me if I'm right: - on startup do_sync() is called - in do_sync() is a call to getTime() - getTime() returns the GETTIME answer - if the difference to system time is greater than max_drift (5sec) then a setTime() -> SETTIME sequence is

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Sonntag, 27. November 2016 00:07:26 UTC+1 schrieb Tom Keffer: > > A dead battery shuts down the Vantage completely but, once replaced, weewx > will immediately set it to the correct time. > I asume this is done by GETTIME / SETTIME combination. During my try I never saw a SETTIME command. Is

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I must be missing something here isn't the answer to just run weewx on the rpi with the attached station acting like a vantage without a logger, and set weewx to software record generation - or does that combination also require a clock in the 'station'? Not sure I really see what the

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Sat, Nov 26, 2016 at 1:36 PM, gustl319 wrote: > > At the moment I don't understand why weewx want to know the time from > Vantage via GETTIME. The only thing I can think of is data logging. I don't > have EEPROM or Flash, so I can't do any logging. This could happen

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

A Dekay board without RTC ignores a GETTIME command a Vantage console does not. Am Samstag, 26. November 2016 21:00:50 UTC+1 schrieb Tom Keffer: > > It's always a much better solution to improve the emulation, rather than > workaround any shortcomings. > Aggreed :-) But to improove the

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

> > > Why does it need a clock time? For datalogging while RPi is down? > > While, in theory, I don't have a problem adding support for the Dekay library to the vantage driver, the solutions we have come up with so far are very ad hoc, and can fail in other ways. For example, if the driver detects

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

This library should do the trick: http://playground.arduino.cc/Code/DateTime But it needs to be set after a power down -- 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

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Samstag, 26. November 2016 19:31:01 UTC+1 schrieb Tom Keffer: > > Just thinking out loud, it is not necessary for the feather to have an > RTC. All that is necessary is that it can keep track of time once it is > set. This is similar to how an RPi works without an RTC. > > Do you know if the

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Sorry. I should have looked up the call instead of guessing. The correct call would be datetime.datetime.now() > When there is no GETTIME answer it ends in syslog.syslog(...) correct? > Then it should return a datetime contruct for the "now" date and time. > Wouldn't that be a solution that

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Freitag, 25. November 2016 21:14:12 UTC+1 schrieb Tom Keffer: > > Yes, alternatively getConsoleTime could be implemented as: > > ​def getConsoleTime(self): > ​return datetime.datetime() > > Does not work! datetime.datetime() needs valid parameters yr, mon, day, hr... I tried

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Dekay Lib: A GETTIME command is always responded with the same static time (Januar 1st 2016 1:00:00). On weewx: getConsoleTime() gets an answer on GETTIME and causes no errors. getTime() corrects the time to time.time() + 0.5 At the moment this works for me. But getConsoleTime() is also

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I'm not following. I don't know how the Dekay libraries work, but I assume they emulate the Davis Vantage API. So, it must respond to a GETTIME command with something, but if the feather has no clock, what is it returning? >From your later note, it sounds like everything is working. What did you

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Just checked index.html Temp and Hum are the same as in the console. So far it looks good. Thanks a lot -- 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

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

It had no effect because GETTIME was still missing. Now with a fake GETTIME and your code I get this. -- 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

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

> > I just tried that. It just seems to have no efect. I'm not familiar with >> phyton. Must I run a compile script? >> > >> ​No. Just restart weewx. Python is an interpreted language. And, please don't just say "has no effect." Some details please. In particular* post the log!* -tk​ -- You

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Freitag, 25. November 2016 18:58:30 UTC+1 schrieb Tom Keffer: > > I don't think it is as simple as removing the GETTIME command. > Just recognized that :-( > Weewx detects the lack of an onboard clock by making a call to the > *driver* function getTime(). If has not been implemented, then

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I don't think it is as simple as removing the GETTIME command. Weewx detects the lack of an onboard clock by making a call to the *driver* function getTime(). If has not been implemented, then it falls back to the system clock. Unfortunately, even if you remove the GETTIME command, the function

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I tried to atach the log file. hope you can read it -- 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,

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

You might not have changed the archive delay - but what is the archive interval set to?? On Friday, 25 November 2016 18:29:55 UTC+2, gustl319 wrote: > I think I can remove the GETTIME command. archive_delay is still at 15 > seconds. I come back later. > > > > Am Freitag, 25. November 2016

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I think I can remove the GETTIME command. archive_delay is still at 15 seconds. I come back later. Am Freitag, 25. November 2016 17:08:48 UTC+1 schrieb Tom Keffer: > > The timestamp for the loop packets come from weewx. So, if the clock on > the RPi is correct, then the loop packet timestamps

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

The timestamp for the loop packets come from weewx. So, if the clock on the RPi is correct, then the loop packet timestamps should be correct. If you run weewx directly from the command line , you can monitor these timestamps and see if they

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Thanks for the fast response. Am Freitag, 25. November 2016 02:47:18 UTC+1 schrieb Tom Keffer: > > Please read the User's Guide, section 3rd party Vantage connectors > and > see if that answers your question. > Unfortunately

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Please read the User's Guide, section 3rd party Vantage connectors and see if that answers your question. If not, come back, but please post the log. Another question: I see bursts of 'Requesting 200 LOOP packets' in debug > mode