I have had the same issue and I have solved it in the same way... El domingo, 14 de abril de 2019, 7:13:33 (UTC+2), Leon Shaner escribió: > > Hey, Cameron, > > You are absolutely right! I did some digging and determined that my > WMR300 is set to 1 minute internal data logging interval, which is good > only for 22 days and has been full since 2016! I confirmed this by moving > my SD card to a faster RPI and starting from a fresh weewx.sdb, and watched > as it pulled in less than a month's worth of data from July of 2016, then > said it was done processing the data from the unit. > > I found the right doc on how to clear the WMR300's internal data log. > I'll set a reminder to do so every other Sunday. > > It would be nice if the WeeWX WMR300 driver could automatically do a > weekly purge of the oldest 1 week's worth of data. That would keep it well > below the default 22 day limit. > > I saw mention in the comments in the driver that the protocol does support > purging of records after reading them. > Of course what is unclear is if you do purge the oldest 1-week worth of > data does that actually free up space to allow the next week going forward? > Probably deserves some experimentation. :-/ > > Anyway, thanks for the note. =D > > Here's that doc. Bear in mind the rain counter is reset separately by > touching the rain display a few times until it say "ACCUM" and then you can > hold the MEM button there to reset it. If it's full it says HHH for the > total accumulation of rain. > > I think I will write a mod and submit it via github to have a warning when > the rain limit is at 90%. =D > > > [image: image1.png] > > Regards, > Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > > On Apr 13, 2019, at 4:05 PM, Cameron D <[email protected] > <javascript:>> wrote: > > Hi Leon, > it seems you still have a problem with the archive data. As far as I > recall the history in the console does not wrap around, so once it is full > then the console never saves any more. > > Your version of the driver is set to clear the history after it reaches > 20% however your last index value looks to me greater than mine was when it > was classed as full. > I suspect there is a bug in the code that means the unexpected high index > count results in it not clearing at all. > > Your firmware version A04 is the same as mine. Did you ever do a firmware > update? > > I would recommend a factory reset because I can't be sure how to tackle a > history clear that has to read beyond what I think is the end of the buffer. > > Cameron > > -- > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/290daa35-a32c-476c-a60b-1aa62851c8d2%40googlegroups.com.
