Cumulus MX FAQ: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:


'''<big>Some of the following is out of date''', it refers to the original beta versions of MX not the latest release, other parts are just hints of what needs to be said ... <big>'''ANY volunteers to UPDATE THIS'''</big>?</big>'''


There is a third party offering for helping you start and stop Cumulus MX  [https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767 on a Raspberry Pi]. There are two other related threads initiated by same author (Jank).
There is a third party offering for helping you start and stop Cumulus MX  [https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767 on a Raspberry Pi]. There are two other related threads initiated by same author (Jank).
Line 22: Line 24:




<big>'''Cumulus MX FAQ'''</big>
'''<big>Some of the following is out of date, it refers to the original beta versions of MX not the latest release


any volunteers to update this?</big>'''


*If you want to use your Cumulus 1 data with MX, and you use decimal commas, you will need to edit the .ini files to change the decimal commas into periods/full stops. The other data files will be OK.
*If you want to use your Cumulus 1 data with MX, and you use decimal commas, you will need to edit the .ini files to change the decimal commas into periods/full stops. The other data files will be OK.

Revision as of 17:10, 26 March 2020


Some of the following is out of date, it refers to the original beta versions of MX not the latest release, other parts are just hints of what needs to be said ... ANY volunteers to UPDATE THIS?

There is a third party offering for helping you start and stop Cumulus MX on a Raspberry Pi. There are two other related threads initiated by same author (Jank).

One problem various people have had is swapping from a Windows environment to a Linux environment. There are lots of new commands to learn, and specifying the interface is different so getting MX to connect to your weather station has been a problem for some.

For setting up your web site see this page first.

There is no guide yet to the MX setting pages. Generally any edit you make to a setting takes effect as soon as you move to next setting, but some only take effect when you next restart Cumulus MX. Most settings have a friendlier interface than the settings for the similar feature in Cumulus 1.

Cumulus MX supports updating to secure web sites, this feature is not yet properly documented.

The use of decimal comma gives rise to various problems mentioned in the forum, as the guidance above says Cumulus MX uses procedures that depend on full stops being used for the decimal point in many log files.

There is confusion between Cumulus 1 symbols for minutes (nn) and the Cumulus MX symbol for minutes (mm) which Cumulus 1 uses to represent months (mm or MM allowed). This is seen in NOAA report names and any web tags that have had a date-time modifier added.

On Cumulus 1, some people used '.' to separate the hours and minutes (HH.nn), this causes problems in MX that only accepts a colon separator (HH:mm). Thus files like the alltime.ini might have a mix of times in different formats.

Another issue raised from time to time in the forum is that if you swap from Cumulus 1 to MX it does not access the old NOAA reports (because the settings in MX were not set to generate same file naming as previously used in Cumulus 1).

Certain versions of Mono give problems, for example the Mono version 5 release has thrown up an issue with some locales and the short month names having an extra decimal point that Cumulus MX cannot cope with. Most of these problems are raised in the forum.



  • If you want to use your Cumulus 1 data with MX, and you use decimal commas, you will need to edit the .ini files to change the decimal commas into periods/full stops. The other data files will be OK.
  • If you are trying to use your Cumulus.ini file from Cumulus 1, you will need to make sure it doesn't contain any non-ASCII characters
  • Cumulus MX doesn't change the fact that you can't run two programs at the same time with the same station, whatever those programs are, unless you have something in the middle handling the multiple connections (e.g. Virtual VP for Davis stations)
  • If a settings screen shows red contents (red text and red boxes), invalid data is present which must be corrected before the form can be sent. One or more items on the page will have an error message.
  • Cumulus MX doesn't create any image files
  • Cumulus MX on Windows requires .NET 4.5 and hence will not run on the obsolete Windows XP
  • The realtime interval on the internet settings screen is in milliseconds
  • There is currently no 'diary' and hence also no snow recording
  • The requirement to run as root/administrator may possibly be removed at some point
  • When you install a new version of Cumulus MX (i.e when upgrading from one version to another), be sure to copy all of the files from the release zip file into your MX installation, and force a refresh of the interface pages in your browser. You can optionally just copy the files that I name as having changed in the announcement, but the risk is that I might have missed a changed file from the list. No settings or data are overwritten by the update.
  • Some setting changes don't take effect until you restart Cumulus MX
  • Note that the change to date/time formats in webtags also applies to NOAA report file formats., if you carry over your old settings
  • The 'extra files' editor updates automatically when a field is changed. You can press 'enter' in a text field to get it to update, or move to another field
  • The remote filename for an 'extra file' must include the path (if required) as well as the file name, just as in Cumulus 1. It does not use the 'directory' setting automatically
  • If you are using your 'old' Cumulus.ini file, make sure your 'ftp site' section is [FTP site] with 'site' in lower case
  • Davis stations sometime supply 'error' values such as 255 for wind speed. Cumulus ignores these and may log some of them to the diags file, if you have debug logging turned on
  • Serial device names on Linux are not COM0 etc as in Windows. You need to specify something like /dev/ttyUSB0 - do a dmesg at a command line prompt and look for the actual device name from your adapter. If dmesg says your cp210x converter (as on Davis stations) is attached to ttyUSB0, for example, you need to put /dev/ttyUSB0 for the serial port name in MX. You can set the serial port name in the MX user interface, but if for some reason you want to do it by editing Cumulus.ini, note that the item in MX is called ComportName (which is a string, for the full device name, e.g. COM1 or /dev/ttyUSB0) rather than 'Port' which is just an integer. If you have not run MX yet, this item will not exist, so you will need to add it (in the [Station] section).
  • If you are having problems after upgrading to Windows 10, see this post - https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=14148
  • Cumulus MX will not run on Windows IOT
  • The Dashboard, Now, and Gauges pages all get their data using web sockets (on port 8002). If they are not displaying data for you, you have some issue somewhere on your system preventing that from working - a firewall issue, or perhaps a browser issue. If you can't get web sockets working on your system, you could switch to using Ajax for the data. See the announcement for build 3032 for instructions.
  • If you want to use a twitter.txt file and include any characters not in the 7-bit ASCII set (e.g. degree symbols or accented characters) you need to save the file as UTF-8 (without 'BOM')
  • As with Cumulus 1, if you have extra web files configured, only tick 'process' for those files which have web tags in them, i.e. they need processing.
  • An "error [object Object]" in your browser when you try to change settings is usually caused by using a version of Mono which does not support comma decimals, but can also be caused by an invalid setting
  • Twitter have changed their authentication method, and Cumulus is now unable to perform the initial step of obtained the authentication tokens. The fix requires significant change to the code and I have no forecast for this