Hi Simon, That is odd that the console timestamp is always odd minutes and the other is always even. What archive interval are you using, if the 'other' is always even is your archive interval two (or some multiple of two) minutes? How often does the console update, every 2 minutes (seems an awfully long period if it does) and perhaps it just started on odd minutes. Not familiar at all with the station/console I am afraid.
Since you are using interceptor you can actually get the interceptor driver to log when and what it is seeing from the console as well as what it is sending to WeeWX. Just edit weewx.conf and set debug = 1, save weewx.conf then restart WeeWX. You can tail the WeeWX log in a terminal window if you wish to transcribe data while watching the console. Only thing is to watch what units are being displayed. Tag wise $span (assume the _ is a typo/cut-paster artefact) should work, $span was developed to provide aggregates across a span in time, for example $span($week_delta=2).outTemp.max would display the max outside temp over the last two weeks. Omitting the $xxxx_delta parameters *should* give you the current value of the observation since the span of values that are considered is just the current value. However, it it was me I would just use $current.windSpeed.raw and $current.windGust.raw to display the average wind speed over the archive period and the highest wind speed seen during the archive period respectively. Gary On Tuesday, 3 March 2020 09:45:39 UTC+10, Simon Davies wrote: > > Hi Gary, > > The console data is timestamped with odd minutes , but the other data is > timestamped with even. I'd prefer it if they were the same, but I'm not > sure how to sync them. I checked the console clock and its correct. > > The driver I'm using is > *[Interceptor]* > * # This section is for the network traffic interceptor driver.* > > * # The driver to use:* > * driver = user.interceptor* > > The tags in the report i'm using are > *$_span.windSpeed.max.raw, and $_span.windGust.max.raw* > > > I've read the wiki entry page and I'm now suspicious that the tags I'm > using are wrong. May be this will explain the discrepancy with the values > shown on the console. > > Thanks Simon > > > On Monday, March 2, 2020 at 1:25:43 PM UTC, gjr80 wrote: >> >> Hi Simon, >> >> Easy one first; you cannot run WeeWX both as a daemon and directly with a >> single station, it's one or the other. >> >> As for the data, a few observations. All of the speeds on rows where >> usUnits == 1 are in miles per hour. The console data is of course km/h. The >> ARCHIVE and REC rows are km/h and miles per hour respectively and they >> should be the same speeds but in different units, windGust is but windSpeed >> is not. There is a large discrepancy between the console data and any other >> data though the console data is timestamped at least one minute after any >> of the other data. >> >> I guess there is still a lot of variables. In an archive record sense >> WeeWX considers windSpeed to be the average wind speed seen over an archive >> period, windGust is seen as the highest wind speed seen over an archive >> period. When you start looking at loop data it comes down to what the >> station and driver output. is the loop windSpeed the average over the loop >> period or a point in time value. What is windGust in a loop context, the >> highest wind speed seen over a loop period (given the data above I don't >> think that is the case) or the highest value seen over some unknown period. >> You have not said what driver you are using (I believe there is more than >> one that supports your station). Also what tags are you using in the report >> that provides the ARCHIVE row? Finally, what does the console display >> values mean, particularly the wind gust value. You might find this wiki >> entry <https://github.com/weewx/weewx/wiki/windgust> interesting. >> >> Sorry, no real answers and just more questions. >> >> Gary >> >> On Saturday, 29 February 2020 22:47:54 UTC+10, Simon Davies wrote: >> >>> Hi Gary, >>> >>> yes the LOOP DATA is taken when running weewx directly. (normally I use >>> the daemon process, I don't seem to be able to run the daemon process and >>> the weewx directly at the same time). >>> >>> For the units I've added an extra column to the table, as there are >>> some variations. >>> Also I've added an extra row for the "REC:" records taken while running >>> weewx directly. The archive data is not from querying the database >>> directly. I have a report that produces this file. >>> >>> *Timestamp* >>> >>> *Wind Gust* >>> >>> *Wind Speed* >>> >>> *Source* >>> >>> *units* >>> >>> *recorded* >>> >>> 2020-02-27 18:27:24 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.310686368325 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 2020-02-27 18:27:32 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.310686368325 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 2020-02-27 18:27:40 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.49709818932 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 2020-02-27 18:27:56 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.062137273665 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 2020-02-27 18:28:12 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.12427454733 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 2020-02-27 18:28:27 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.12427454733 >>> >>> LOOP DATA >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> 27/02/2020 18:29 GMT >>> >>> 4 >>> >>> 0.4 >>> >>> CONSOLE >>> >>> km/h >>> >>> visually >>> >>> 27/02/2020 18:28:00 GMT >>> >>> 1.100002734 >>> >>> 0.400000994 >>> >>> ARCHIVE >>> >>> km_per_hour (weewx.conf) >>> >>> weewx reports >>> >>> 2020-02-27 18:28:00 GMT >>> >>> windGust: 0.683510010315 >>> >>> windSpeed: 0.295152049909 >>> >>> REC >>> >>> usUnits: 1 >>> >>> weewx direct (stdout) >>> >>> Simon >>> >>> -- 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/b71a179e-3e4d-4b96-9c6b-0bb85d963e4e%40googlegroups.com.
