SteelSeries with WeatherCat

[UncleBuck]

Hi Mark and others,
New to this forum but have been working on getting these gauges and your scripts to work with WeatherCat.

I have made some changes to the script but would like them to be integrated into your scripts rather than create a whole new branch of scripts.

Please let me know if you are up for this idea.

Regards,
Col.

[mcrossley]

Can you give some idea of what the changes are? Maybe a link too?

[UncleBuck]

Mark,
The changes were things like putting in a couple of extra if and switch statements so that you could set weather Program to 0=Cumulus, 1=Weather Display, 2=WeatherCat

Added a variable _wcatlink for the specifying of the realtime file.

I have tried to make very minimal changes and am working with the developers of WeatherCat to get them to expose more tags for the realtime file.

The site I am working with is http://weather.kcsolutions.com.au/gauges-ssT.html and the .js file is at http://weather.kcsolutions.com.au/gauge ... /gauges.js

Col.

[UncleBuck]

I also fixed a bug that was causing the Tempunit not to be displayed correctly and have found an anomaly that I am not sure if it is the gauges script or the steel series script.

On my page of gauges, if you change the Pressure units to kPa, the pressure gauge shows duplicate numbers. This might even be some setting that I have missed somehow but I am not at all sure.

Col.

[mcrossley]

I think I'll let the solution 'mature' a little before considering including it in the base release - when all the required tags are supported for instance.

The duplicated scale values on baro when in kPa are because I force 'zero' decimals on kPa (so it should be 102.0, 102.5 etc), I'll change this to 1 decimal place for version 2.0.2 which I need to get out v. soon anyway to fix a WD problem with km/h wind speeds.

[UncleBuck]

Hi Mark,
I have been working with the developers of WeatherCat and nearly all things are working now as they have exposed more tags as you can see at http://weather.kcsolutions.com.au/gauges-ssT.html

I do have another question for you regarding the way the gauges work, specifically the wind direction:
The other day I had a ten minute wind variation between 005 deg and 355 deg (actually it was between 355 deg and 005 deg) but it appears that the way the gauges work the min direction becomes 0 deg and the max direction becomes 350 deg.
This seems to cause the red backing of the gauge (i.e. variation indicator) to show as nearly all red, is this standard behaviour?

Col.

[mcrossley]

...the min direction becomes 0 deg and the max direction becomes 350 deg.
This seems to cause the red backing of the gauge (i.e. variation indicator) to show as nearly all red, is this standard behaviour?

Yes it is normal, the METAR standard is to round the wind variation to whole 10 degree increments.

[steve]

Isn't there another issue here, though, regarding which is the 'from' value and which is the 'to' value? It's up to the software supplying the values to get them the right way round.

[UncleBuck]

That's what I'm getting at....
According to the Wiki:
<#BearingRangeFrom10> The 'lowest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini), rounded down to nearest 10 degrees
<#BearingRangeTo10> The 'highest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini), rounded down to nearest 10 degrees

Doesn't this mean that if the wind is varying around north that you will always get a min of 0 and a max of 350, hence the guage will actually show the variation as being 0 to 350 rather than 350 to 0.

Am I not getting something here and misunderstanding how it all works?

Col.

[steve]

If the wind is varying from 350 to zero, then the <#BearingRangeFrom10> value should be 350 and the <#BearingRangeTo10> value should be 0. That's what the 'clockwise' in the descriptions is getting at.

[UncleBuck]

I must be dumb..... I still don't see how the software (by that I mean Cumulus) can understand that 350 deg is lower than 0 deg.

For arguments sake, lets say the variation was from 355 deg to 11 deg. How would Cumulus know that 350 deg is the low value it should pass through and 10 deg is the high value?

As another example, what if the variation was from 274 deg to 94 deg? How does Cumulus know that the wind swung around through North or through South? In this example which would be high and which would be low?

Col.

[steve]

It uses the (calculated) average bearing. It knows that 355 is 'less' than 11 because it knows that the average bearing is north-ish rather than south-ish. Any readings in the half of the compass anticlockwise from the average are regarded as 'lower' values, and any in the other half of the compass are 'higher' values.

[mcrossley]

Sorry, with you now, yes as Steve says you would calculate the variation as a from-to pair of values that 'contains' the current average direction. For Davis sensors the variation is usually quite small and the from-to is obvious, not always so with the Fine Offsets.