You need to use wee_device (or the sw that came with the station) to set the hardware interval on the station. There is no setting by pressing the buttons/menu on the station itself.
On Monday, 2 April 2018 00:05:29 UTC+3, Rick Hewett wrote: > On Sun 01 Apr Andrew Milner wrote: > > 1. if weewx.conf in [stdArchive] section says hardware records then > > check the archive interval on the wh1080 and set to required > > interval using wee_device > > > 2. if weewx.conf in [stdArchive] section says software records check > > the archive interval is set correctly in weewx.conf > > I think the relevant settings are: > > polling_interval = 60 > > archive_interval = 300 > > record_generation = software > > However, as the problem seems to have started after some sort of > hardware glitch, think that's probably where the problem lies... > > > check what the log says when weewx is started - it should give station > > interval, weewx.conf interval, and which interval will be used if > > there is a difference > > Ah! After a re-start this afternoon it reported: > > Apr 1 14:45:11 duma weewx[14214]: engine: Record generation will be > attempted in 'software' > > Apr 1 14:45:12 duma weewx[14214]: engine: The archive interval in the > configuration file (300) does not match the station hardware interval > (1800). > > Apr 1 14:45:12 duma weewx[14214]: engine: Using archive interval of > 1800 seconds (specified by hardware) > > Previously, it was saying: > > Mar 22 00:29:51 duma weewx[8841]: engine: The archive interval in the > configuration file (300) does not match the station hardware interval > (60). > > Mar 22 00:29:51 duma weewx[8841]: engine: Using archive interval of 60 > seconds (specified by hardware) > > Time to go hunting for the setting in hardware, I guess... > > > On Sunday, 1 April 2018 13:29:22 UTC+3, Rick Hewett wrote: > >> It's weird. Things were working fine until a few days back. Then > >> something went wrong with my WH1080 and I had to power-cycle it. Since > >> then it has been producing readings for weewx only on the hour. No > >> changes on the computer side, as far as I can tell (unless something > odd > >> happened in the day or two it was struggling to get sense from the > >> hardware), so seems to be a hardware problem, but even a full reset > >> hasn't cleared it... > >> > >> Any software things I might check in case something has been corrupted > >> there? The config is unchanged and looks sane. > >> > >> -- > >> 73, Rick, M0LEP > >> > >> > > > > -- > 73, Rick, M0LEP > > -- 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.
