Cumulus Support

Hi there,

I finally set up my new Raspberry Pi 2 (with the current Raspbian Linux OS) this week and started CumulusMX.

It did start with a clean new installation, but not with my old Cumulus 1.9.4 Data configuration.

Having read very carefully all the posts in this forum I assume this is because of the "comma problem" with the german locale and mono.
-> I don't care too much about this restrictions and will be using a clean new Setup.

The issue I am reporting (and didn't read here in the Forum) is the following:

I can't see (and therefore also not set) any entries in the section "Station Settings" in the GUI of CumulusMX.
In the other sections of the settings (e.g. Internet Settings) it is working fine.

Any idea what's wrong?

best regards,

willyweather


Some background info:

CumulusMX Build 3024
Raspberry Pi 2 + WS1080 weatherstation
Raspbian Wheezy
Mono 3.2.8
used Browsers: Local browser of RasPi, Microsoft Explorer (Win8.1PC), Firefox (Win8.1 PC), Safari(iPad)

So are you running CumulusMX under the German locale?

When I used the local browser from the pi I had the same issue , the interface is working bad with this browser I use chrome for linux now.

Ok, good to hear, that also others had this problem

Yes, I am running CumulusMX under the German locale, but I was trying also to switch to the english locale temporarily... Don't remember too good, but I think this didn't change things too much.

I'll try Google Chrome asap (but I don't like this idea too much...)

Thanks for the quick response

I don't know much of the German Locales but look at this thread from slasmusic it might be usefull https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13753

If you are still having problems, note this instruction from the 'Beta testing - please read' post:

"If you have an issue with the user interface, use the F12 developer console in your browser. The interface uses http calls and websockets to get its data (websockets are used for 'live' data), so look at both, and look at the javascript console - problems are often obvious. 'Fiddler' is a useful free tool that I use myself as an alternative - http://www.telerik.com/fiddler - it can show you the communication between the browser and the server as an alternative to the browser developer console."

The Epiphany browser on the Pi works fine for me with MX (with UK settings).

willyweather wrote:Ok, good to hear, that also others had this problem

Yes, I am running CumulusMX under the German locale, but I was trying also to switch to the english locale temporarily... Don't remember too good, but I think this didn't change things too much.

Hi, good mornng. I struggled with the same Problem in the past days.
You wrote, that you are using the following Hard/Sodtware

Raspberry Pi 2 + WS1080 weatherstation
Mono 3.2.8

PLease read my post from yesterday: Cumulus MX - Raspberry PI 2 - https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13753
The most mportant thing is to install the most current version of Mono.
I am running: mono --version |grep version -> Mono JIT compiler version 4.0.1 (tarball Tue Apr 28 01:50:29 UTC 2015)

I am not sure, but as far as I remember, I had the same issue with the "empty" Station settings Page after I first saved the config.
This was getting better, when I updated mono.
Solution for you:
Update Mono as explained in my post or Steve's post
Delete Cumulus.ini once you seeing any Problems
The Cumulus.ini file will be created automatically after you start Cumulus.
Once you get it started again, check all Settings in the Station Settings Page and look for values which are having a . - for example 0.7 (Solar - transmission factor) change these settings to a full nunber withou a .

If you made a mistake and the settings are disapearing again, stop CumulusMX use nano and search for "RStransfactor" and set it to a full number like "1"

If you like, use my instruction mentioned above.
Since yesterday, I have my Station up and running and I am using all my old 5 year old Data from Cunulus1 in CumulusMX.

Hi there - many thanks for the quick and interesting hints ...

I'll first try to upgrade mono again.
(I had read the suggested posts already before, but failed to upgrade mono as described. I have to check what I did wrong.)

I posted this error description because I didn't see the link to this old mono version.

I'll also try Steve's hint, if necessary, but I am no HTML specialist at all (only very small basic knowledge) ... So this will be my 2nd choice.

I'll let you know my results asap.

Wilfried

willyweather wrote: (I had read the suggested posts already before, but failed to upgrade mono as described. I have to check what I did wrong.)

I updated my instruction (https://cumulus.hosiene.co.uk/viewtopic.p ... 30#p107030) based on your concern. Thanks for the hint.
Jan

willyweather wrote: I'll also try Steve's hint, if necessary, but I am no HTML specialist at all (only very small basic knowledge) ... So this will be my 2nd choice.

Don't worry about trying to understand what the F12 console is telling you, just post any obvious error messages here.

Hi there,

I finally made it (with your great help, thank you)

With your (Jan) new, improved instructions which now are matching better the original posting of Steve I could load and activate mono V4.01.

For some reason I had ot use "autoremove" instead of "remove" in my case (?) which I learned by carefully reading the Linux console messages...


But back to the topic of this post:

Yes, the described issue in this topic could be fixed by updating mono to the latest Version 4.0.1 !


-> mono 3.2.8 with german (and other?) locale probably won't work with CumulusMX

--> Topic closed, thank you !

Wilfried

p.s. : In addition, I had also to modify the transmission factor from "0,8" to "1" as described in the other postings.

willyweather wrote: --> Topic closed, thank you !

Hi Wilfried

Maybe you want to use my Start|Stop Script I created today to start CumulusMx as a kind of Service without having an open Console window

Please see this Post and let me know, if it works for you. Feedback is always appreciated
https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767

Oh yes, I'm willing to use those scripts asap, thank you.
I was wondering anyway what happens, if I start cumulus in a user console window and I will terminate this user console later ... I assume, that cumulus will stay active, but how do I stop it, if e.g. I have to disconnect the weather station. (I am a Linux Newbe, as you can see

Probably your scrips will help

Wilfried

Hello Wilfried

you wrote: I was wondering anyway what happens, if I start cumulus in a user console window and I will terminate this user console later ... I assume, that cumulus will stay active

and this is exactly not the case. Cumulus is running Interactive and closing the console session where you started CumulusMX will also close Cumulus. Lets compare it with a DOS Window in Windows for example. you can open a DOS Window and insert commands etc, but in the moment you close this DOS window, everyhting running in this Window will stop working.

but how do I stop it, if e.g. I have to disconnect the weather station. (I am a Linux Newbe, as you can see
but god thanks, Linux give some ways to also handle programs started "interactive".
Please read this, to get more information about the screen command: http://wiki.ubuntuusers.de/Screen It's a german webpage.

So my Script is using "Screen" to start CumulusMX and running in the background, also when the Console is being closed
The advantage of this method is, you don't need a connected Keyboard and Monitor at your RaspberryPi, you can run it in so called "Headless" mode, without any input device (Keyboard , Monitor)
You can simply connect to your Pi by using SSH (Putty) - starting CumulusMX and close the Putty session (Cumulus is further running)

The only Problem is indeed, how to stop Cumulus later when is is being "screened"
So Screen is giving some commands to find out all "screened" sessions, for example: screen -ls

My Script, is doing 2 things
First, finding out, if there is a running CumulusMX Session which is being screened
If so - it is asking to stop this CumulusMX Session. If you enter No, it will further run, if you enter YES, it will find out, which ScreenSession is being used and sending a CTRL+C to stop CumulusMX normally.
The Script is waiting for further 5 seconds and sending a KILL command to the MONO Program (this is, because in the past I had problems that Mono is still running with 100% CPU and Cumulus never stops after sending CTRL+C)

The second thing the Script is doing is:
If you call the script again, it will find out, that CumulusMX is not running and will start CumulusMX

So it works for me and I made some further improvments in the Output of the status messages when calling the script.
I also added some better error handling - Thats the reason why the verison number is increasing

so give iot a try and let me know if it is doing strange things