cloudy cloudy

Recent Posts

Pages: [1] 2 3 ... 10
1
WD Feature Suggestions / Getting Historical Data with WeatherFlow
« Last post by hankster on September 25, 2017, 10:53:20 PM »
Brain,

Just talked to the guys at WeatherFlow and they say you can request past data from the WeatherFlow servers via the REST interface. Could this be implemented?

I've had WD flatline a couple of times and it would be nice to be able to fill in the data that was missed.

Thanks!
2
Chatter / Re: Wasting a lot of time with WML
« Last post by garyghj on September 25, 2017, 10:17:58 PM »
Hi everyone,

There are times when frustration takes over common sense and manners, and I was frustrated, however I cannot apologise enough to Chris. After only a few email exchanges and a very minor adjustments by Chris  my problems were sorted and everything is running well. 

Gary
3
Custom Templates and Scripts / Re: Zone Forecast
« Last post by saratogaWX on September 25, 2017, 10:01:36 PM »
Also, you could revert to V4.02 of the script to avoid the beta entirely, and switch back to V5.02 when the NWS decides to actually implement the new forecast.weather.gov based on the API.  Still unknown when that will occur.
4
Graphics / Re: Problems with Saratoga mesomaps
« Last post by saratogaWX on September 25, 2017, 09:59:03 PM »
Hi John,
It looks like you have an original V2 of the AJAX-WD-World template set, so unless you update to a V3 Base-World/WD-plugin set, the check-fetch-times.php?show=versions may not be very helpful. You can get a complete set of the needed files to convert V2 to V3 by using the V2->V3 conversion tool -- it's a fairly exacting process to merge your mods into the new files, but afterwards, you'll be able to easily use the update tool to keep the common scripts fresh and tidy. 

But.. more to your issues cited in the first post:
1) The Settings.php entries are being ignored
Code: [Select]
   143: $SITE['rmMapUseDefaults'] = 'false';
   144: $SITE['rmNETID'] = 'SCWN';
   145: $SITE['rmMapZoom'] = '6';
   146: $SITE['rmMapCenter'] = '56.0, -4.0';
should be
Code: [Select]
   143: $SITE['rmMapUseDefaults'] = false;
   144: $SITE['rmNETID'] = 'SCWN';
   145: $SITE['rmMapZoom'] = '6';
   146: $SITE['rmMapCenter'] = '56.0,-4.0';
note that 'false' is not the same as false in PHP.  The former is a string and in a logical compare evaluates as true (that is non-zero), while the latter is a logical constant and evaluates as false (a zero).  That's likely the reason why your override settings were ignored.


2) the rotating conditions seem to skip values.  This strange behavior is caused by two instances of
Code: [Select]
setTimeout("RMNET_rotate_content()",RMNETrotatedelay); being run with slightly different start times.  That routine should run once after the page is loaded to begin the rotations of the display (and on your page it seems to be running two instances).
I noticed that a 'Pause' and then a 'Run' gets it back to doing an orderly transit of the rotating conditions with no 'skips'.  I'll have to dig into your code a bit more to isolate the cause.

3) regarding the clientraw.txt location, that's not something that the mesonet-map scripts use directly -- the data for the mesonet-map comes directly from the selected regional network (SCWN in your case), and the SCWN is doing the 'pull' of your clientraw.txt every 5 minutes.  If the location of the conditions file is incorrect on the SCWN, that's something that Martin at SCWN to correct.  Currently, the SCWN is showing
Quote
Details for Angus Auchterhouse (SCWN-stations-cc.txt record 27):

<!-- type='CR' RawDataURL = 'http://sidlawweather.co.uk/clientraw.txt' -->
<!-- curl fetching 'http://sidlawweather.co.uk/clientraw.txt' -->
<!-- HTTP stats: RC=200 dest=77.72.0.162 port=80 (from sce=10.0.18.197)
Times: dns=0.000 conn=0.006 pxfer=0.006 get=0.007 total=0.013 secs -->
<!-- headers:
HTTP/1.1 200 OK
Last-Modified: Mon, 25 Sep 2017 21:30:23 GMT
Content-Type: text/plain
Content-Length: 751
Date: Mon, 25 Sep 2017 21:51:55 GMT
Accept-Ranges: bytes
Server: LiteSpeed
Connection: Keep-Alive
-->
<!-- CR time to fetch: 0.013 sec (200 OK) -->
<!-- webserver timesync=7 sec 'Mon, 25 Sep 2017 21:51:55 GMT' -->
<!-- age=1292 sec 'Mon, 25 Sep 2017 21:30:23 GMT' -->
<!-- metric='12345 7.7 7.7 61 11.6 98 1022.0 9.0 67.0 602.0 0.00 0.38 21.6 58 100.0 1 0.0 0 0 6.0 -100.0 -100.0 -100.0 -100.0 -100.0 -100.0 -10 -10 -10 22 30 29 Auchterhouse-22:30:29 0 0 25 9 100 100 100 100 100 100 12 11.6 13.5 14.2 11.3 1 Night_time/Scattered_clouds_ 1.0 8 9 9 9 8 7 7 8 9 9 9 8 9 9 9 9 8 9 9 9 22.3 11.3 738.6 25/9/2017 17.4 13.1 14.2 11.3 0.0 6 6 7 8 7 8 7 8 8 7 11.5 11.4 11.4 11.6 11.6 11.7 11.7 11.7 11.7 11.6 9.0 9.0 9.0 9.0 9.0 9.0 9.0 9.0 9.0 9.0 14.2 11.3 11.6 18.0 0 --- --- 60 0 0 0.0 0.0 -100 0 0 0 0 0.0 23.4 19.8 9.5 1022.0 1017.6 14 21:49 05:00 16.6 6.2 13.8 10.9 10 2017 -17.8 1 0 1 62 52 73 66 56 59 60 73 66 69 0.0 255.0 7.7 11.4 56.53194 3.06917 5.0 100 96 9.3 00:01 0.0 0.0 0.0 0.0 0.0 0.0 365.3 16:40 00:01 69 !!C10.37S55!!' -->
<!-- station using CR units C,kts,hPa,mm by default -->
<!-- convertWind(7.7) kts [7.7 kts] to '9' MPH -->
<!-- convertWind(7.7) kts [7.7 kts] to '9' MPH -->
<!-- CR[48]=1 .. trying METAR EGPN for conditions -->
<!-- METAR='EGPN' -->
<!-- curl fetching 'http://tgftp.nws.noaa.gov/data/observations/metar/stations/EGPN.TXT' -->
<!-- HTTP stats: RC=200 dest=140.172.138.79 port=80 (from sce=10.0.18.197)
Times: dns=0.000 conn=0.129 pxfer=0.129 get=0.131 total=0.261 secs -->
<!-- headers:
HTTP/1.1 200 OK
Date: Mon, 25 Sep 2017 21:52:02 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Last-Modified: Mon, 25 Sep 2017 19:24:15 GMT
ETag: "46b8b00-41-55a0881134be6"
Accept-Ranges: bytes
Content-Length: 65
Vary: Accept-Encoding
Content-Type: text/plain; charset=UTF-8
-->
<!-- EGPN time to fetch: 0.261 sec -->
<!-- EGPN='2017/09/25 19:20 EGPN 251920Z VRB02KT 3000 BR SCT004 14/14 Q1023' -->
<!-- age=9122 sec '2017-09-25 19:20:00 GMT' -->
<!-- metar 'EGPN' saved in local cache -->
<!-- metar too old.. ignored -->
<!-- condition begin: '','','','' -->
<!-- fixupTime in='6:00a' tfixed='6:00a' out='06:00' -->
<!-- fixupTime in='7:00p' tfixed='7:00p' out='19:00' -->
<!-- fixupTime in='22:52' tfixed='22:52' out='22:52' -->
<!-- condition using: time2='22:52' as night for sunrise2='06:00',sunset2='19:00' -->
<!-- Angus Auchterhouse 27 data='11.6,98,ENE,9,9.0,1022.0,Rising Slowly,,,11.3,9,1506375023,0.013' -->
so it is pulling from ./clientraw.txt and not ./live/clientraw.txt so contact Martin to make that change.

Hope this helps...

Best regards,
Ken
5
Custom Templates and Scripts / Re: Zone Forecast
« Last post by SkyBoy on September 25, 2017, 07:59:17 PM »
I think I'll go with the zone forecasts until the "beta" is ready. I have had those wacky forecasts 3 or 4 times in the last month.

Thanks Ken   :wink:
6
Creating Weather Web Sites / Re: Create a simple html page with 2-second refresh
« Last post by niko on September 25, 2017, 07:40:53 PM »
I PM'd you some code that may help.
7
Weather Station Equipment / Re: Davis VP2 Anemometer Stopped Working
« Last post by FPGAgeek on September 25, 2017, 07:35:36 PM »
Thanks guys.

Looks like it was the AC-DC PSU as I have powered the Davis Anemometer transmitter with just a CR123 battery and it works as expected. The wall power plug was not a Davis instruments one, I am guessing the voltage output regulation is noisy - I will investigate further when I get a little more time.
8
Graphics / Re: Problems with Saratoga mesomaps
« Last post by Ralph1 on September 25, 2017, 07:33:58 PM »
Hi there Ken,

Many thanks for your rapid reply. I made the correction you spotted in the ajaxWDwx-settings.js file but it didn't seem to make any difference.
However running the latest version of check-fetch-times.php?show=view indicates that my website needs an enormous amount doing to it mainly in updating out of date files but also quite a few were missing.  In my current system there are quite a few changes from the original Saratoga system to allow data from unusual hardware to be displayed.

Presumably you can run "check-fetch-times.php?show=view" on my website and you will see what I have seen. Not sure if I have the energy to make all the changes and I'd be worried that some self made changes might no longer work. So I'm not quite sure where this leaves me. Perhaps I should just update one file at a time until we find the culprit but it looks as though the system has changed vastly since the time of my original set-up. I guess I knew that but didn't realise it was so critical for this particular application.

Many thanks again,

John
9
WD Bug Reports / Re: Problem with Selected Tags
« Last post by FPGAgeek on September 25, 2017, 07:30:13 PM »
for #3, I use %timeoflastrainalways% and %dateoflastrainalways% which according to tagslist do not get "reset".

Thanks Martyn, I have now added these tags in to my weather report templates.

you could try setting a minimum temperature limit in the offsets/limits setup in WD

I have tried this for a few days but no change.
My wdisplay.ini contains the following entry which I guess is linked to this tag:

[Daily low 6 hour night]
number=0


Are there any files I can check that may give any clues to my issue?
10
Creating Weather Web Sites / Create a simple html page with 2-second refresh
« Last post by mihec on September 25, 2017, 07:11:26 PM »
I don't really have experience with html/js/php programming but just did a simple page for my station. Besides a main html, I added a realtime page using steel gauges. WD is uploading customclientraw.txt to my server every 2 or 3 seconds.
Is there a (really) simple way to set up a html/php page that would update the parameters from the customclientraw.txt in the same way as the steelgauges do? I could modify the steelgauges page but I just want to keep my page really simple and small.
Thanks!
Pages: [1] 2 3 ... 10
cumulus