[weewx-user] ultimeter setup troubles

2017-01-13 Thread Eelco F
Hi all, I'm trying to setup my second weatherstation project (first was a Davis). This time it's an ultimeter 2100. weewx is 3.6.2-1 I connect the serial interface and put the ultimeter in datalogger mode. I ran weewx both directly, and as a service. weewx.conf is almost out of the box, except

[weewx-user] Re: WeeWx-WD SS gauges config

2017-01-13 Thread gjr80
Ok, the setup seems OK as far as I can tell; I can see all your scripts just where you say they are. However, there is a path issue. If you do a view source when you have wxssgauges.php open in your browser you will see the following lines (circa line 570):

[weewx-user] Re: WeeWx-WD SS gauges config

2017-01-13 Thread Dan'l B
Attached. I am assuming you meant the contents of gauges-ss-basic-inc.php, which is what I have attached. On Friday, January 13, 2017 at 4:03:56 PM UTC-5, gjr80 wrote: > > Ok, the setup seems OK as far as I can tell; I can see all your scripts > just where you say they are. However, there is a

[weewx-user] Re: ultimeter setup troubles

2017-01-13 Thread Eelco F
Allright, thanx for your quick reply. This is what I got: Jan 13 22:19:50 server weewx[3331]: * Starting weewx weather system weewx Jan 13 22:19:51 server weewx[3344]: engine: Initializing weewx version 3.6.2 Jan 13 22:19:51 server weewx[3344]: engine: Using Python 2.7.12 (default, Nov 19

[weewx-user] Re: ultimeter setup troubles

2017-01-13 Thread mwall
On Friday, January 13, 2017 at 3:38:05 PM UTC-5, Eelco F wrote: > > > I just can get it to work. Am I missing some point here? > Or should I put the ultimeter in modem mode device first so the driver can > set the correct setting? > the drive will attempt to put the ultimeter in modem mode, so

[weewx-user] Re: rapidfire work on usb conected acurite display and 5-1 sensor?

2017-01-13 Thread Andrew Milner
That's what Matthew said to do . On Friday, 13 January 2017 19:58:01 UTC+2, wxwatching wrote: > Ok, I installed git and cloned a copy of Weewx to my RPi2. Do I install it > using the setup.py method? > > Thanks, > Anthony > > On Friday, January 13, 2017 at 9:00:05 AM UTC-5, mwall wrote: >>

Re: [weewx-user] Re: rapidfire work on usb conected acurite display and 5-1 sensor?

2017-01-13 Thread Thomas Keffer
If you're just experimenting, you need not install it at all. Just go into the directory where you cloned weewx, and run it directly from there, giving a path to your weewx.conf file. For example, cd ~/git/weewx ./bin/weewxd /etc/weewx.conf -tk On Fri, Jan 13, 2017 at 9:58 AM, wxwatching

[weewx-user] Re: WeeWx-WD SS gauges config

2017-01-13 Thread gjr80
Ok, I what has happened now. The wxssgauges.php page is distributed with the WD plugin for the Saratoga templates, wxssgauges.php has a variable that is set to refer to the location of the SteelSeries Weather Gauages scripts. When I donwloaded and installed the gauges some time ago (v2.4.4 -

[weewx-user] Re: WeeWx-WD SS gauges config

2017-01-13 Thread Dan'l B
With the Saratoga templates in /st, the ss gauges dir is /st/ssg. > $ssgDir is set to '/ssg/web_server/' > $ssgDir = './ssg/web_server/'; All the files generated by WeeWx-WD are uploaded to /st And the path to the ccr file in gauges.js is: > realTimeUrlWD :

Re: [weewx-user] Matching rain corrections with weewx and Weather Underground

2017-01-13 Thread Thomas Keffer
The value sent to wunderground is calculated directly from the database. It's the sum of all rain that fell during the last 60 minutes. So, if you're happy with the values of 'rain' in the database, then you should be getting the same at wunderground. -tk On Fri, Jan 13, 2017 at 6:21 PM, J

Re: [weewx-user] Matching rain corrections with weewx and Weather Underground

2017-01-13 Thread Thomas Keffer
I have no idea how they factor in RapidFire values: they don't publish that. RF is a black box, that they don't seem to be paying much attention to. -tk On Fri, Jan 13, 2017 at 6:56 PM, J wrote: > Hmm, perhaps I just didn't wait long enough then. My values definitely >

Re: [weewx-user] Matching rain corrections with weewx and Weather Underground

2017-01-13 Thread J
Hmm, perhaps I just didn't wait long enough then. My values definitely diverged, so I removed the correction so avoid having to correct a lot of data. Does wunderground calculate an intermediate value from uncorrected values sent via rapidfire, which then get replaced once per hour by the

[weewx-user] Matching rain corrections with weewx and Weather Underground

2017-01-13 Thread J
Hi, I'm trying to apply some corrections to my rain data but am running into an issue with getting Wunderground data to match. I want to adjust my rain corrections based on wind data -- I'm compensating for undercatch during high winds due to my rain bucket's higher than typical elevation

[weewx-user] Re: ultimeter setup troubles

2017-01-13 Thread Steve2Q
If you try what Matthew suggests and everything appears ok, may try a different driver. There were several iterations of the Ultimeter driver, and I had problems with the last one (it would not keep proper time on my 2100 console). I am not saying this will take care of your problem, as

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread gjr80
No problems Andrew. As I see it the issue is (put succinctly): why does $day.windSpeed.max == $day.windGust.max ? I do not believe they should. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
I have been monitoring the loop packets and the data appears to be correct. It is providing windGust and windSpeed and these are being correctly reported for the archive interval. I believe Gary has the same results with a different station type so it is unlikely to be a station problem. --

Re: [weewx-user] Re: Possible calculation error?

2017-01-13 Thread Thomas Keffer
"dwhile" I have been able to replicate the problem where archive_day_windSpeed.max is always equal to archive_day_windGust.max. Let me dig into it deeper. -tk On Fri, Jan 13, 2017 at 6:48 AM, dwhile839 via weewx-user < weewx-user@googlegroups.com> wrote: > Ok Added that code and turned debug

[weewx-user] Re: rapidfire work on usb conected acurite display and 5-1 sensor?

2017-01-13 Thread wxwatching
Thanks for the info. I will read up on git and install on my RPi2. Having programmed in VB, ASP, PHP, and even a little WebDelphi for years, perhaps the learning curve won't be too steep. Anthony On Friday, January 13, 2017 at 9:00:05 AM UTC-5, mwall wrote: > > On Friday, January 13, 2017 at

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread gjr80
On Saturday, 14 January 2017 00:00:06 UTC+10, Andrew Milner wrote: > > Gary - the daily table for windSpeed is called archive_day_wind not > archive_day_windSpeed > Um, actually it is called archive_day_windSpeed. archive_day_wind is the daily sumamry for the vector wind. mysql> SELECT *

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
Gary - my humble apologies indeed I just saw that there was another page to archive on my phpmyadmin screen - which had two more tables - archive_day_windSpeed and archive_day__metadata!!! had never noticed the additional page prompt before!!! I really am grovelling now and apologising

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
well my windspeed max and windgust max are different. On Friday, 13 January 2017 16:26:27 UTC+2, gjr80 wrote: > Doubt it is a station issue, I have a VP2 and get the same results. I > think this is more likely and issue of how the accumualtors work and > process the various wind obs. > > On

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
That is correct - we are in agreement. They are different in the archive, but are both the same value and time in the archive_day tables. Looks to me as though either the station or the driver could be the source of the problem and running with debug set may shed some more light. On Friday,

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
Ok Added that code and turned debug on. Will monitor to see if it occurs. Interestingly the following appears: Jan 13 14:46:50 weather weewx[8513]: wmr100: Bad USB report received. Jan 13 14:46:50 weather weewx[8513]: * could not detach kernel driver from interface 0: No data available Jan

[weewx-user] Re: cm or Zoll

2017-01-13 Thread gjr80
Hi, I presume you are talking about the add sensor entry in the wiki? Assuming this is the case. There are 3 places in weewx where units are critical. The data coming from the station, the data being stored in the database and the data

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
Here is the relevant bit from the template (the template is large!) "wlatest":"$current.windSpeed.formatted", "lastestmax": "$current.windSpeed.max.formatted", "wspeed":"$hour.windSpeed.avg.formatted", "test":"$hour.windSpeed.max.formatted",

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
I wouldn't expect the lines to be the same as that is not the problem. The gust figure will normally be higher than the average. The problem lies with $day.windSpeed.max - this is a single figure so not plotted on the graph. The docs say that this is calculated by averaging the windspeed over

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
Ok Assuming that weewx does rounding in the normal way (anything below .5 rounded down and .5 and above rounded up) then there is definitely a calculation error. I have looked at the source data in the database and for today the maximum wind speed recorded (up to now) is 13.421656358 (as

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
a) What formatting is specified in skin.conf - for use by .formatted? b) when you say "as recorded in the database" - are you referring to the archive table or the archive_day_windspeed table? c) what is your archive interval? d) what is the result of the following sql commands: select

Re: [weewx-user] Re: Possible calculation error?

2017-01-13 Thread Thomas Keffer
The documentation for $day.windSpeed.max is wrong. It should read: The max average wind speed. The wind is averaged over each of the archive intervals. Then the maximum of these values is taken. It has been changed in commit 35ad31

[weewx-user] Re: Data from imported db not showing up

2017-01-13 Thread Andrew Milner
Stop weewx, backup (just in case) and delete ALL your NOAA files, restart weewx and the old ones from 2014 together with the later ones will be recreated On Friday, 13 January 2017 14:21:37 UTC+2, Ξ wrote: > Hello, > > I had an separate weewx.sdb with some data from 2014, I imported it in my

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
If you set loop_hilo in std archive section of weewx.conf then only the archive data will be used for the daily high/low figures. If loop_hilo is set true then both loop and archive data can affect the stats. It looks as though you have it set to true, and the loop data from a gust is

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
Hi you are correct both return the same value and the same dateTime stamp. -- 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

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
When you say setting loop_hilo has had no effect - what happened? You need to restart weewx after changing weewx.conf, and it will only affect new values processed after the change, and would only be seen if you have a higher average wind in an archive period than the already recorded high or

[weewx-user] Re: Data from imported db not showing up

2017-01-13 Thread Ξ
Ah, nice, that was an easy one, thanks a lot! :) -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
select max(windSpeed) from archive where dataTime > x; (for today)13.8690394820237 select max(windGust) from archive where dateTime > xx;(for today) 15.4348987783812 select max, maxtime from archive_day_wind where dateTime = xx; (for today)

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread gjr80
The SteelSeries Gauges template fields are correct (well the 10 min average actually uses a 1 hour average but that is either here nor there). The fact the maximum windSpeed recorded in the archive is lower than the what you get with $day.windSpeed.max is not surprising. The windSpeed values

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
Gary - as far as I can see from the results from the queries I asked for the issue seems to be resolving why day_archive_wind has the same value AND time as day_archive_windGust when in the archive the max for windSpeed and windGust are different values. On Friday, 13 January 2017 15:30:36

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
Just to confirm setting loop_hilo to false has had no effect. If you want me to try anything please let me know - I was until recently an Associate Professor in Computer Science so programming isn't a problem for me!! -- You received this message because you are subscribed to the Google

[weewx-user] Data from imported db not showing up

2017-01-13 Thread Ξ
Hello, I had an separate weewx.sdb with some data from 2014, I imported it in my current weewx.sdb the following way: 1. stopped weewx 2.1. sqlite> .output weewx.sql 2.2. sqlite> .dump 2.3. sqlite> .read weewx.sql 3. Just in case (wasn't sure if necessary) I dropped and rebuilt the daily

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread dwhile839 via weewx-user
The first - I think Andrew has succinctly stated the problem above: "Gary - as far as I can see from the results from the queries I asked for the issue seems to be resolving why day_archive_wind has the same value AND time as day_archive_windGust when in the archive the max for windSpeed and

[weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
Gary - the daily table for windSpeed is called archive_day_wind not archive_day_windSpeed On Friday, 13 January 2017 15:52:55 UTC+2, gjr80 wrote: > Andrew, > > The issue here is windSpeed and windGust being identical. > $day.windSpeed.max and $day.windGust.max come from archive_day_windSpeed

[weewx-user] Re: rapidfire work on usb conected acurite display and 5-1 sensor?

2017-01-13 Thread mwall
On Friday, January 13, 2017 at 8:12:22 AM UTC-5, wxwatching wrote: > > mwall, > > Thanks for the info. I don't suppose there is a date set yet for that > release? If it is still sometime away, I am not adverse to install a > development version, although I have never installed from github and am

Re: [weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
Tom Mine seems to be correct: *+ Options* Partial texts Full texts Relational key Relational display column Show binary contents Show BLOB contents Show binary contents as HEX Hide browser transformation Geometry Well Known Text Well Known

Re: [weewx-user] Re: Possible calculation error?

2017-01-13 Thread Andrew Milner
Tom Mine seems to be correct - data from wh2800 via fineoffsetusb Showing rows 0 - 19 (20 total, Query took 0.0017 seconds.) [dt: *1484258400 - 1482616800*] SELECT archive_day_windSpeed.dateTime as dt, date(archive_day_windSpeed.dateTime), archive_day_windSpeed.max, archive_day_windGust.max