Steel Series Gauges - how to reduce the refresh interval

[RayProudfoot]

Do you see the same as me? Everything fine until you change C to F in the box at the bottom of the page at which points temps go negative.

It's broken as soon as I go to your webpage, without changing units.

The gauges web page doesn't need to be continually uploaded by Cumulus. It's a waste of resources if nothing is changing .

Delete the cookie and try again. I understand your point but it's not that causing the problem.

[De Hout]

I installed this many years ago and no longer have the original zipfile, so I can't figure out which files belong to the Steel Series.
I can think of two options:

1. Like Mapantz suggested: First, back up all the old files, then delete all files in the steel-series directory (there might be files present from the original CU1 gauges) and try a new installation.
2. Wait for a response from Mark.

[RayProudfoot]

Derk, I've reverted to my gauges.js as I wanted to test the settings in mine. I still had the problem with yours so gauges.js itself isn't the problem.

I've set some gauges to false, saved gauges.js and refreshed my gauges webpage. The changes are reflected. Here are the entries in gauges.js for the temperature scale:-

tempScaleDefMinC : -20,
tempScaleDefMaxC : 40,
tempScaleDefMinF : 0,
tempScaleDefMaxF : 100,

To me that suggests that when C is selected (the default) the minimum will be -20 and the maximum will be 40. But look at what is shown. The Fahrenheit numbers are used, not Celcius.

Temp.jpg

Why doesn't it reflect the values in gauges.js and why, when I select F the temperature is "broken" with negative values that are only fixed when I delete the cookie for cheadlehulmeweather.co.uk?

This is perplexing.

[RayProudfoot]

Hi Derk,

We posted at the same time. I'll try removing all existing files in the SS folder and start again. Fingers crossed.

At least I'm learning things so it's not a total waste of time.

[De Hout]

As long as you back up the files, nothing is lost.

[De Hout]

FYI: This is at the bottom of the source of my gauges-ssT.htm
One script is slightly different compared to yours.

Code: Select all

<!-- Included Scripts -->

  <!-- Google CDN hosted JQuery library -->
  <script src="https://code.jquery.com/jquery-1.11.1.min.js"></script>
  <!-- or... -->
  <!-- Local JQuery library, do not use if your containing page already pulls in a copy of JQuery -->
  <!-- <script src="scripts/jquery-1.11.1.min.js"></script> -->

  <!-- Combined steelseries.js & tween.js -->
  <script src="scripts/steelseries_tween.min.js"></script>

  <!-- Once you have customised this scripts to your requirements you should minimise
       and concatenate them into a single file in the same order  as below -->
  <script src="scripts/language.min.js"></script>
  <script src="scripts/gauges.js"></script>

  <!--Optional Wind Rose scripts -->
  <script src="scripts/RGraph.common.core.min.js"></script>
  <script src="scripts/RGraph.rose.min.js"></script>

[RayProudfoot]

FYI: This is at the bottom of the source of my gauges-ssT.htm
One script is slightly different compared to yours.

The difference would appear to be the parameters used for the jquery command. 1.11.1.

I tried those and the result was a blank gauges page. I had to revert to my original ones. Maybe down to MX and C1.

Looking at your gauges I notice it defaults to C and the min and max values are for C. On mine the default is still C but the min / max values are for Fahrenheit. It’s that where the problem lies. But without expert help from @mcrossley I’ll never figure out where the problem lies.

Deleting the SS files may solve it but I won’t know what the problem was. As a former programmer that goes against the grain.

[Mapantz]

It's still doing the same when I look at your gauges Ray..

Did you replace your realtimegaugesT.txt with the version that you downloaded? Try it if you didn't

[RayProudfoot]

It's still doing the same when I look at your gauges Ray..

Did you replace your realtimegaugesT.txt with the version that you downloaded? Try it if you didn't

Did you delete the cookie and do a forced reload? Works here.

Why change what works? Here’s my realtimegauges.txt. Looks fine to me.

https://www.cheadlehulmeweather.co.uk/r ... gauges.txt

[sutne]

Why change what works?

I thought that was the reason some people still use Cumulus 1?

If I could be impudent: If you had used the same efforts in updating your system to CumulusMX as you have these last days, wouldn’t you had an updated system that is much easier to maintain?

[RayProudfoot]

Why change what works?

I thought that was the reason some people still use Cumulus 1?

If I could be impudent: If you had used the same efforts in updating your system to CumulusMX as you have these last days, wouldn’t you had an updated system that is much easier to maintain?

Several reasons why I won’t change to MX.
1) My dedicated netbook bought in 2009 still runs perfectly. The XP OS won’t run MX.
2) I haven’t a clue how to run MX or have any knowledge of how it works.

My system requires minimal maintenance. It was only my desire to increase the refresh rate for wind that started this discussion. As it turns out I could have achieved that on the earlier software. It just required the knowledge in knowing what to change. The change would have involved the same files irrespective of what version I was running.

Some more thinking about this problem. The temperature gauge is clearly initialised for Fahrenheit but the selector is for Celsius. That, I think, is the cause of this problem. If it was a more serious problem why isn’t wind, pressure or rain affected? It’s only with temperature.

I can prove this. Current temperature is 6.9°C. Assuming that is treated as Fahrenheit by the code then the Celsius equivalent is -13.9°C.

Guess what is shown when I select C. -13.9°C.

There must be an incorrect setting that is setting Fahrenheit rather than Celsius as the default.

Any experts out there that can analyse my gauges.js?

[Mapantz]

Did you delete the cookie and do a forced reload? Works here.

I did. Still the same.

[RayProudfoot]

Did you delete the cookie and do a forced reload? Works here.

I did. Still the same.

Strange. Works here on both W11 and an iPad running Safari.

I’ve deselected gauges-ssT.htm from being processed. I don’t think that’s the problem. My earlier message has pointed at the problem.

[mcrossley]

OK a lot of catching up for me to do here. But it appears that a lot of confusion is arising from trying to use the new CMX web site files with Ray's C1 installation.

I'll do some reading of the thread and looking at Rays web web site as it is now...

[RayProudfoot]

OK a lot of catching up for me to do here. But it appears that a lot of confusion is arising from trying to use the new CMX web site files with Ray's C1 installation.

I'll do some reading of the thread and looking at Rays web web site as it is now...

Thanks Mark. Didn’t know they were just for CMX.