Offsets MX with commadecimal system

[nitrx]

It looks like the latest build workds with comma's but the offsets will not pick up fine a minus sign is not accepted well it does not behave so , when I use -1.000 for temp it adds 1 degree instead of substracting, the wind mulitipliers I've set to 1.700 but after saving the go to 17.000 I did set the UV multiplier to 0.4000 but it changes back to 4 so I get too hihg temps to high wind and too high UV.

The dashboard shows the comma's thats good , I'm not sure about the rain offsets because no rain oh and the offset for temp I did set to 2.200 but this is been reset to 22.000

All running on win 7 with dutch regional settings.

Do you need additional info Steve ?

[steve]

Can you tell me whether in the ini files from Cumulus 1 and Cumulus MX have commas or decimal points in them?

I'll look at the issues you've found, thanks.

[nitrx]

Cumulus 1 uses comma's

Code: Select all

[Offsets]
PressOffset=-0,899999976158142
TempOffset=-2,09999990463257
HumOffset=0
WindDirOffset=35
InTempOffset=0
WindSpeedMult=1,75
WindGustMult=1,75
TempMult=1
HumMult=1
RainMult=1
UVOffset=0
UVMult=0,349999994039536
WetBulbOffset=0
WetBulbMult=1
DavisCalcAltPressOffset=0

Cumulus MX has no comma's at all

Code: Select all

Offsets]
PressOffset=0
TempOffset=-1
HumOffset=0
WindDirOffset=0
InTempOffset=0
UVOffset=0
WetBulbOffset=0
WindSpeedMult=17
WindGustMult=17
TempMult=-1
HumMult=1
RainMult=1
UVMult=4
WetBulbMult=1

By the way in the console I fill them in with decimal points because comma's are not accepted there.

[steve]

That's a bit odd. When I switched my PC to French settings, I was getting decimal points in the ini files, and it all seemed to be working OK. I'll have to do more investigations. I did think that C1 used commas in the ini files, that may be a problem if I can't get MX to use commas in the ini files too (for moving from C1 to MX with the same files).

The forms package (used for the config screens) doesn't support decimal commas, so decimal points have to be used.

[nitrx]

When I edit the ini in MX manually with notepad++ the offsets works fine after starting MX but when i do a change in the console they are set back to the 'wrong values'.

[dane]

Installed a clean 3011 on my RPi, using default language en-GB, and everything went very well.
Excellent work, thank you, Steve! Great promises for the future of Cumulus.

Then thought: what the heck - let's try a localised Danish version.
So I copied all my old Cumulus1 files to the RPi, renamed cumulus.ini to Cumulus.ini, changed the internet location from cumulus to cumulus3, and started CumulusMX with -lang da-DK.
Got a few messages about "invalid token", but CumulusMX came up.
It ran for a while, displaying "interesting" numbers, and seemed to die when I tried to display the gauges from the console screen.
I had been warned there would be problems, so was not surprised there were a few .
I attach a couple of files to give you something to work with, Steve...
You may want to look at: http://www.ibtest.dk/cumulus3/index.htm for more info.
Attached:

20150122-163833.txt

Cumulus.ini

todayyest.JPG

[steve]

Some interesting weather you have there. I think one of the problems is that Cumulus 1 writes decimal commas to the ini files, and MX uses 'invariant' decimal points. You could (if you want to experiment) try editing your C1 ini files (Cumulus.ini and the ones in the data folder) and doing a global replace from comma to 'period', and see if MX likes them a bit better.

[dane]

My RaspberryPi is going to be a dedicated CumulusMX console, so I think I'll leave it as an en-GB machine, that way avoiding all the localization problems.
I'll convert a basic set of my Cumulus1 files to en-GB and use that for testing the RPI - at the moment there are no facilities in CumulusMX like Select-a-graph, so not much point right now in converting all my old monthly files since Sept. 2008.

[steve]

It looks like the latest build workds with comma's but the offsets will not pick up fine a minus sign is not accepted well it does not behave so , when I use -1.000 for temp it adds 1 degree instead of substracting, the wind mulitipliers I've set to 1.700 but after saving the go to 17.000 I did set the UV multiplier to 0.4000 but it changes back to 4 so I get too hihg temps to high wind and too high UV.

This should be fixed in 3013.

[nitrx]

Yes this work fine great job

I've copied the datafiles from C1 to MX changed the decimalcomma in the ini files to decimalpoint. cannot read/load the monthly data in the console before march 2013.... the dayfile.txt loads fine.

Edited in this post the monthlyrecord and alltime/yearrecord are fine now (forgot to refresh the page )

[steve]

cannot read/load the monthly data in the console before march 2013

Do you get any errors in the diags file when you try this? Could you zip up and upload one of the log files that won't load? Never mind - I can reproduce the problem - thanks.

[nitrx]

Hi Steve the older logfiles read fine now but there was a strange error in the diags something 'looking on your PC' I've no idea what it is

diag attatched

[steve]

It just looks like you tried to access the log for Feb 2009, and you don't have one? I need to put in some checks for files not being present.

[nitrx]

It just looks like you tried to access the log for Feb 2009, and you don't have one? I need to put in some checks for files not being present.

I did , and that file is not availble indeed.