Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
gwheelo wrote:I failed to mention that it was also necessary to change line 50 of gauges_french.js as well so that the LANG.dew.info.web variable was consistent throughout.
The 'LANG.dew_info_web' is the wrong variable - it should have been (and will be in futur versions) 'LANG.dew_web' (as it appears in line 1420 of the the 'gauges.js' script and in line 50 of the 'gauges_french.js' template).
The variable 'LANG.dew_info' (as well as all the variables with the '_info' ending) is only used to display the gauge title inside the mouse-hover graphic images - this allows for the display of a longer title (longer than the maximum 11 characters allowed for the title inside the gauges).
CheroKiwi wrote:Is there a way to turn the forecast off.
Ron, the 'Sunny' displayed in the forecast gauges is the forecast as produced by Cumulus...
There is no switch as such to turn off the display of the forecast ... but you can certainly edit your 'wxgauges.php' to either remove the forecast line completely or place a PHP condition to tell the page to display the forecast only during day time hours (when the probabilities of being sunny are greater ). On one of my test pages, I have moved both the LED and the count down time to the bottom of the page in order to increase the length (width) of the forecast gauge to (try to) contain the longer forecasts produced by my Vantage Pro2 console.
steve wrote:The word "Sunny" does not appear in the default forecasts as produced by Cumulus.
Thanks Steve - the 'Sunny' appearing in Ron's forecast gauge comes from the webtag '<#forecast>' - can a La Crosse WS1081 weather station produce its own forecast texts (such as produced by the Vantage weather stations)?
gemini06720 wrote:can a La Crosse WS1081 weather station produce its own forecast texts
Yes, they supply a number from zero to 2 inclusive, which are equivalent to "Rainy", "Cloudy", and "Sunny", respectively. I think it's probably just a representation of an icon on the console display, in which case I would expect some sort of sun icon to appear on the console at the time that the station is sending the "Sunny" forecast - unless the console does something different at night? I could probably change Cumulus to convert "Sunny" to "Clear" between sunset and sunrise - in fact, I will.
gwheelo wrote:I will correct all scripts on my static test site to conform.
I guess it should be mentioned in the next updates that the 'language' template should be used when translating into another language - I have sent Mark a modified french language template as well as a 'default' template to be used for language translation (the language inside that default template is english) - I have attached the ZIP should you want to check/use the templates.
I use the <#currcond> tag to provide METAR data from the local airport. In realtimegaugesT.txt I've changed the <#forecast> tag to <#currcond>, thus giving the current METAR rather than Cumulus' forecast.
A few changes this time, so please read the readme file.
Here are the changes
1.1.0
Now works with Cumulus 1.9.1, adds autoscrolling for long forecasts, changes how multiple
languages are handled.
Updated steelseries.js
- updated to release 'standard release' 0.7.2 from Gerrit
- fixed logic around LED blinking
- fixed singleLCD panel clipping text with long thin displays
- added autoScrolling, automatically scrolls long messages that do not fit in the display,
short messages are still displayed statically.
Updated gauges.js
- added 'hot' scale shading (above 45C, 110F)
- added check for Cumulus build number in 'station off-line' code
Updated realtimegaugesT.txt
- added cumulus build number
Updated parseRealtime.js
- updated for extra build number field
Updated gauges-ssT.htm, gauges-ssT-Fr.htm
- added hidden span to force early .ttf font download from web servers that do serve .woff files
- added include for language.js
- updated to HTML 5 standards
Added language.js file
- contains language translations, default file contains English & French
I have attached the file to the first message in this thread so we always know where the latest version is!
Thanks, that is good to know - though of course now I look at your page you have a short forecast that doesn't need to scroll
Edit: Do you really have such a low pressure variation at your location? (about 1008 - 1027) You could change the limits for the pressure gauge to bring the minimum up to say 990.
Ray has pointed out that there was a slight problem with the temperature popup data in French (and other languages that are masculine/feminine).
So version 1.1.1 has been posted, only the "gauges.js" file has been changed, and you only need to bother upgrading from 1.1.0 if you intend to use languages other than English.
ss v1.1.1 now married to my gauges page without a hitch except one feature. The status window changes language for all messages on command except when the text overrides the window width and starts scrolling. Something is happening or not happening when autoscroll goes into action. Text starts jittering with multiple languages while scrolling. Obviously my language scheme is incompatible with autoscroll. This is not a big thing for me as all my forecasts fit within the window - but I like the feature and would love to implement on my site. Any ideas? One other question - how might I change the status text color - I'm thinking "red" for instance.
Currently I change the status language with:
if (gauge_baro) { doBaro(); }
if (gauge_rain) { doRain(); }
if (gauge_rrate){ doRRate();}
if (gauge_hum) { doHum(); }
if (gauge_wind) { doWind(); }
if (gauge_wdir) { doDir(); }
setStatus(LANG.forecastlong[cumulus.forecastnumber]); //set for testing