Cumulus Support

The date is not an issue. The RS trans factor is, as the max is 1. The error message for that will be "The maximum value for this field is 1". Change it to 0.8 and the form should be OK.

It looks like another bug in Mono which has yet to be fixed - https://bugzilla.xamarin.com/show_bug.cgi?id=4242

steve wrote:The date is not an issue. The RS trans factor is, as the max is 1. The error message for that will be "The maximum value for this field is 1". Change it to 0.8 and the form should be OK.

Hello Steve sounds good, but I did not changed this RS trans factor I assume the German local made from 0.8 to 8
Everytime I change this setting from 8 to 0.8 or 0,8 it will be saved again as 8
But changing it to 1, solved the Problem

If you correct it and send it, then reload the settings screen, you should find the error is back again because of the bug in Mono in the JSON conversion code.

slashmusic wrote:But changing it to 1, solved the Problem

Yes, that would work. But you will have the same problem on other settings screens which have decimals, and they may not be so easy to work around.

steve wrote:

slashmusic wrote:But changing it to 1, solved the Problem

Yes, that would work. But you will have the same problem on other settings screens which have decimals, and they may not be so easy to work around.

Yes but you stated, that the new Mono version for ARMv7 (Raspberry Pi2) should fix the Problem or am I wrong ?

Different problem.

steve wrote:Different problem.

okay, anyway, I am here to make further tests with this combination Pi2 and German Locale).
Until now, there is no further file or settings throwing errors when starting with german Locale settings.

I will let you know, when seeing further problems.
Thanks so far for this good, quick support

steve wrote:

slashmusic wrote:But changing it to 1, solved the Problem

Yes, that would work. But you will have the same problem on other settings screens which have decimals, and they may not be so easy to work around.

Steve...I worked a little bit more with this Version and completed the most of the Setup Screens.
For example: the NOAA Settings and Calibration settings.
There are values, which sometimes need decimals but personally for me, it makes no difference if I setup a thresold like: 29,0 or 29.0
When I insert a value with a comma, somewhere on these Pages, you immidiately give a warning: This value is not a number.
So you are forcing people to use a . as a delimiter instead of a Comma. I am abolutely okay with it.
A workaround for you could be, that you don't accept any delimiter like dot or comma.
Are there evalues which need to be so precise that people need to insert a value with a delimiter?
(I hope, this question is allowed)

I can not remember any value which need to be so accurate having a delimiter....
So personally I am okay using a value like 10 instead of 10.3 in the calibration settings for example......

however, I completed most of the settings pages, I did not use any comma in the settings and I am fine with the result.

My txt files are still filled with comma seperated values and Cumulus is okay with it.
I removed all comma's from the ini files and I don't use any Comma's in the settings pages.
Everything is working fine until now. also the Websites are being updated fine also when using a different Template.
I am still testing but the result can be visited at http://jankreutzer.de/sites/wetter/index.htm

the only thing I am still struggling with is these character settings to display the German special characters like aüö I used in my translated Pages
Edit: Also solved this Problem.
Explanation (and maybe some people are not really aware of this)
All my old HTML Pages are created with this Character settings: charset=iso-8859-1
Cumulus is and should be set to UTF-8 but the Pages are still not showing the correct Characters for exmaple öäü in German pages
Solution: Open all html pages in the web folder of the CumulusMX installation like indext.htm etc with an editor and change the Character settings from your original charset to charset=utf-8.
the most important thing when you save the modified file in your editor is, that you also switch the encoding in your editor to UTF-8. Most editors are saving in Ansi by default.
Maybe this helps some poeple struggling with the same Problem

slashmusic wrote:So you are forcing people to use a . as a delimiter instead of a Comma. I am abolutely okay with it.

I don't have any choice, it's not my code. It's a javascript library and it doesn't support comma decimals.

Are there evalues which need to be so precise that people need to insert a value with a delimiter?

Some people apparently use three decimal places for some of the calibration settings.

the only thing I am still struggling with is these character settings to display the German special characters like aüö I used in my translated Pages

Do you mean on your web pages? You need to make sure that you have the correct utf8 setting in Cumulus for your pages.

Hi Steve...before I leave for today (giving up)
I Cumulus 1.x people were able to make their own translations and the file used for this was called: strings.ini.
In the default installation I can not find this file.
Can I use the old one from my cumulus1 also for CumulusMX ?
Or in case I am blind and oversee the file somewhere in the folder, where exacty should it be located?

You can use the same one. A strings.ini file is not supplied with either Cumulus 1 or MX, you create your own in both cases based on the supplied samplestrings.ini file, see http://wiki.sandaysoft.com/a/Strings.ini

steve wrote:You can use the same one. A strings.ini file is not supplied with either Cumulus 1 or MX, you create your own in both cases based on the supplied samplestrings.ini file, see http://wiki.sandaysoft.com/a/Strings.ini

thanks, perfect. It works.......sorry, it was long ago, I configured it on my old Cumulus.

Next question, Problem

I have Problems, working with Calibration - Multipliers - Settings.
Example:

Starting Cumulus with: sudo mono CumulusMX.exe -port 9999 -lang en-GB
going to Wind speed and adding: 1.500 - saving config, reload page, Multiplier is still on 1.5

Starting Cumulus with: sudo mono CumulusMX.exe -port 9999 -lang de-DE
going to Wind speed and adding: 1.500 - saving config, reload page, Multiplier is on 15.000

Okay, here is something wrong, but I will do the ofllowing
going to Wind speed and adding: 0.1500 - saving config, reload page, Multiplier is still on 15.000
going to Wind speed and adding: 0.0150 - saving config, reload page, Multiplier is still on 15.000
So I can insert whatever I want, Cumulus is always changing back to 15.000

this is strange.

workaround:
Starting CumulusMX with -lang en-GB - doing all the settings on the Calibration - stop Cumulus MX and resart with German Language and never touch this page. CumulusMX is workign with the Mulutpliers I added with the English settings.
Is this also something happened because of Mono ?

I don't understand why you think it's strange? It's exactly the same problem as the 'transmission factor'. I said that you would have the same problem on other screens!

steve wrote:I don't understand why you think it's strange? It's exactly the same problem as the 'transmission factor'. I said that you would have the same problem on other screens!

Okay, you are right.
Finally, I got everything up and running.
Some setitngs are a little bit tricky, if someone not using english settings but all in all, I will replace the old cumulus with the new Beta now.

I finally configured it as a mix if UI and edit the cumulus.ini file.
Thanks so much again for the support so far.

Some basic things left:
I have sometimes problems, stopping CumulusMX.
CTRL+C will not bring mono to stop. The only way to get it stopped is using the "sudo kill -9 pid" command. I could not finally find out, when this happens, but maybe one scenario is, if you are on the dashboard webpage and try to stop Cumulus. Can anybody reproduce ?

Second question: Does anybody have written a init.d startscript for CumulusMx, to run it as a daemon/service start|stop ?