Right - so the almanac is the logger in the station Is the almanac the same as the LOOP data or the REC data? Does weewx build a record for the database or does the hardware provide the REC data for the database record?
It seems to me that you probably need to run with debug enabled (maybe debug=2) and see what exactly happens when you stop and start weewx. You certainly need to determine exactly what is passed from the station to the driver and onward into weewx and the database under those conditions. Of course weewx will be using whatever is in the database for generating plots - so knowing what exactly is in the database (compared to in the logger) may prove helpful information. Sorry - but there seem to many unknowns to just guess - maybe the TE923 author has additional input/information. Good luck On Tuesday, 20 August 2019 09:55:13 UTC+3, mph wrote: > > I am sorry, I don't have acces to my weewx database now. > I will check and post the database data later. > > The almanac is the set of historic records stored in the weather station > internal memory. > It can be (and actualy was) obtained by calling wee_device --history > The almanac records are very similar to - if not the same as - loop > records obtained via USB connection by weewx. > > > mph > > Dne úterý 20. srpna 2019 7:46:20 UTC+2 Andrew Milner napsal(a): >> >> what are the database values for rain? >> >> not sure what the almanac is - or do you mean database? does your >> database store rain, ticks or both? >> >> >> >> On Tuesday, 20 August 2019 08:02:07 UTC+3, mph wrote: >>> >>> Ok, >>> >>> I've decoded all the almanac data and there is an excerpt: >>> >>> 01:19:00, 265 ticks >>> 01:49:00, 267 = 2 >>> 02:19:00, 268 = 1 >>> 02:49:00, 271 = 2 >>> 04:49:00, 272 = 1 >>> 05:49:00, 273 = 1 >>> 07:49:00, 274 = 1 >>> 08:19:00, 275 = 1 >>> 10:49:00, 276 = 1 >>> 19:19:00, 279 = 3 >>> >>> As you may see, my almanac has 30 min interval, all times are local time. >>> Between 01:19 and 03:00 local time there are 5 ticks recorded, but weewx >>> shows just 4 ticks. This is one missing tick. >>> >>> The fact is, that at 02:17 local time my RPi is backing up the weewx >>> database to local file server. It took less than one minute and I am doing >>> it "safe way" - weewx stop/DB copy/weewx start. >>> But if the weewx/te923 driver is losing tick in that period, then theres >>> something wrong - current station data always show actual tick count and it >>> is correct. >>> Seems there may be a problem with "tick-delta" calculation. >>> >>> Maybe upon service restart the weewx/te923 driver should read the latest >>> recorded tick count and then start to compute the delta ticks from current >>> loop record. >>> >>> >>> mph >>> >>> Dne pondělí 19. srpna 2019 22:36:46 UTC+2 mph napsal(a): >>>> >>>> [image: dayrain.png] >>>> Hello, >>>> >>>> today it was a bit rainy here and my weather station Garni 857 (Hideki >>>> clone) is showing the 24h rain volume as 9.8 mm (14 bucket tips of 0.7 mm >>>> each). >>>> But weewx shows just 7.9 mm of rain (12 bucket tips with weewx/te923 >>>> driver bucket volume correction 0.7 -> ~0.65 mm). >>>> >>>> Seems that 2 of the bucket tips are lost by weewx/te923 driver. >>>> >>>> The today weewx rain history is visible on the attached image. >>>> Please, see attached txt file with almanac read from the station using >>>> wee_device --history. >>>> Only the changes of the "rain" value are included. >>>> At the end of the file is copy of the result of wee_device --current >>>> call. >>>> >>>> The "rain" field changed from 265 to 279 tips in last 24 hours. >>>> But weewx image shows just 12 tips. >>>> >>>> My weather system is backed-up and there's no drop or loss in the >>>> weather data. >>>> >>>> Any suggestions? >>>> >>>> Thank you >>>> Pavel >>>> >>> >>> -- 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/8bb408b0-33f4-4483-89c5-e8c4b95fb2c3%40googlegroups.com.
