Maplin W96GY (WH1080) minimum log interval

[Lloyd]

I'm not near my systems at the moment so can't look for myself. Can anyone tell me what the minimum log interval is? I thought it was 5 minutes, but someone has just suggested to me that it is less than this.

Thanks

Lloyd

[steve]

It's five minutes.

[Lloyd]

I have discovered that it can be set to 1 minute, and has been running like that for just under a day.

Lloyd

[jim-easterbrook]

I have discovered that it can be set to 1 minute, and has been running like that for just under a day.

I'll be interested to hear if you run into any reliability problems.

[steve]

Actually, the data format document does say '1 to 240 minutes', so presumably the station is happy to run at an interval of 1 minute, even if Easyweather doesn't offer it as an option.

[aussiewmr]

I have discovered that it can be set to 1 minute, and has been running like that for just under a day.

Lloyd

How did you achieve that Lloyd? My guess is you have some custom software writing to the mem location as per Jim's memory map.

Cheers
Phil

[mcrossley]

I set my interval using Jim's python scripts - I have to because Easy Weather will not write anything back to my station since my absolute pressure reading went a bit 'wonky'

[Lloyd]

How did you achieve that Lloyd? My guess is you have some custom software writing to the mem location as per Jim's memory map.

Cheers
Phil

I asked my question originally because I was trying to see why wview would not communicate with my W96GY, and in fact would corrupt the weather station so I had to pull the batteries out. Looking through the source I saw that it was writing to the station to set its interval to 1 minute. It turns out that this is quite OK, and I tracked down other issues in the communication that were causing an issue.

So I have now been running like this since Sunday (Wednesday evening now), and have had no freezing. I have restarted wview a few times, but this is only because I'm still developing my setup. It has now cycled round the entire memory, and has looped back to the beginning. I have had a few instances where I have lost comms between transmitter and base station, but I've always had this issue.

My other experience has been with pywws, and that never went more than 3 days, and often failed within a day. (You can't step back through memory on the base station, and have to pull the plug to recover.) That was using a 5 minute logging interval.

I should point out that I can't run cumulus as I'm running from an O2 joggler, which I have installed linux on, as windows does not run well on it. This small low power device happily captures data, and hosts the website under apache. I'd rather leave the joggler on 24x7 than my PC. If I had the option, I would run Cumulus, which I tried briefly.

Lloyd

[jim-easterbrook]

So I have now been running like this since Sunday (Wednesday evening now), and have had no freezing. I have restarted wview a few times, but this is only because I'm still developing my setup. It has now cycled round the entire memory, and has looped back to the beginning. I have had a few instances where I have lost comms between transmitter and base station, but I've always had this issue.

I'll be interested to hear if wview does solve your problem. However, I know that I can go as long as three weeks without a freeze, so give it a bit of time...

My other experience has been with pywws, and that never went more than 3 days, and often failed within a day. (You can't step back through memory on the base station, and have to pull the plug to recover.) That was using a 5 minute logging interval.

I'm sorry it's been so unreliable for you. Was that with 'live logging' or a cron job at hourly (or more frequent) intervals? (Perhaps we should discuss this on the pywws mailing list.)

One of the few certainties (for me) about these freezes is that they are very irregular. They can happen after a few days, or a few weeks, with no apparent change in set up.

My theory (which is mine) is that there's some interaction between two of the three unsynchronised clocks - the 48 second data transmission interval (set by the outdoor sensors), the 5 minute (or other) logging interval (set by the base station) and the computer's USB reading interval. The slow drift of these clocks with respect to each other allows you to go for ages without a problem, or not. I just wish I knew how to solve the problem.