Hi and thank you for the follow up. Exactly this is is the use case but goes down to hard disks standby.
The data base is installed on a RAID5 which during day time does various IOPS during about 60% of the time, but during night is idle almost 95% of the time, hence the disks get parked and the power consumption goes down to 25W total (compared to 70W when disks are spinning). Running weewx every five minutes means that the data must be written in the data base. During the day this is ok. But during the night it means the disks will keep on spinning practically for ever at maximum power consumption. Let us assume for a moment that there is no lock up issue, so to move on with the discussion on parameter values and their practical meaning. Using the last given values (archive=read=5 minutes & poll=30minutes) the expected behavior is not the actual. I expect weewx to contact every 30 minutes the console and receive all the stored 5 minute apart entries of the last 30 minutes (ideally total 6 readings - 5x6=30) The first time I run weewx this exactly what happened. In fact weewx download ALL the stored records updated the database, update WU with all records and created all reports. Following that first run this is not what I see. What I see is weewx waking up every 30 minutes, reading ONE stored record (is it averaging all the records in one record or is it reading only the last record??), updating WU with only that record (indeed I see only 30 minute apart single readings in the WU station's portal) and NEVER updating the local reports. And this is the point I try to short out here. Maybe I am perceiving wrongly the document? Or I might have misconfigured something? But is my expectation correct against those specific settings? Thank you. --- Best regards, ΜΦΧ, Theophanis Kontogiannis Στάλθηκε από το iPad μου 14 Μαρ 2017, 16:43, ο/η mwall <[email protected]> έγραψε: >> On Tuesday, March 14, 2017 at 10:22:46 AM UTC-4, Theophanis Kontogiannis >> wrote: >> I need weewx to contact the console every 30 minutes and download in bulk >> the individual 5 minute appart readings that were storred in the console >> from the station over the last 30 minutes. > > is weewx supposed to be running during the 30 minutes? > > the approach you describe is prone to causing usb lockups. > > each time it initiates a read of the console memory, the driver does a bunch > of short reads in order to synchronize with the console (the console clock > cannot be trusted, and the logger records do not have absolute timestamps). > it can take up to an archive interval to synchronize. the problem is that > every time you try to read the logger memory you increase the chance of > locking up the usb, which results in losing all of the console data. > > the weewx architecture is not designed for the operating mode that you > describe. it is designed to read logger memory at startup, or at every > archive interval. > > it is not designed to read the logger at arbitrary intervals greater than an > archive interval. > > that might be a useful approach for situations where the computer sleeps for > a long period, the occasionally wakes to read some data and upload it. it > would be like the wee_reports utility, but for collecting data. > > could you explain more why you want to use this approach? > > you could write your own python script to do this. one approach would be to > import the fousb driver, then invoke the genArchiveRecords method in the > fousb driver. but i'd probably go with the direct query approach as > implemented in the te923 driver. > > m > -- > You received this message because you are subscribed to a topic in the Google > Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/s1XmmtTP530/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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]. For more options, visit https://groups.google.com/d/optout.
