FAQ: Difference between revisions

70 bytes added ,  20:01, 25 March 2020
m
Line 15: Line 15:


== I use Cumulus 1 and want to move to Cumulus MX ==
== I use Cumulus 1 and want to move to Cumulus MX ==
You can move between versions fairly easily, but you should really read all the guidance in the Cumulus MX support forum. However, here are some key points:
You can move between versions fairly easily, but you should really read all the guidance on the Cumulus [[Cumulus MX|MX page]]. However, here are some key points:
* While Cumulus 1 has a tool to generate graphs itself and then uploads them to your website, the graphs used in Cumulus MX are drawn when the end-user loads the web page, they use Highcharts routines that are free for non-commercial use only, i.e. you may not use MX with these graphs on a company web site.
* While Cumulus 1 has a tool to generate graphs itself and then uploads them to your website, the graphs used in Cumulus MX are drawn when the end-user loads the web page, they use Highcharts routines that are free for non-commercial use only, i.e. you may not use MX with these graphs on a company web site.
* While Cumulus 1 runs as an application that includes a main screen, and other screens, that appear when you start it, Cumulus MX is two separate applications, there is the "engine" that connects to your weather station and processes that data, but there is also a separate user interface that can be viewed on a browser on any device connected to the same local network as the device that runs the engine (for key security reasons this user interface should not be exposed over the wider internet).
* While Cumulus 1 runs as an application that includes a main screen, and other screens, that appear when you start it, Cumulus MX is two separate applications, there is the "engine" that connects to your weather station and processes that data, but there is also a separate user interface that can be viewed on a browser on any device connected to the same local network as the device that runs the engine (for key security reasons this user interface should not be exposed over the wider internet).
* If you want to use your Cumulus 1 data folder with MX, and you use decimal commas in your Cumulus 1 data, you will need to edit the '.ini' files to change, in each stored value, the decimal commas into periods/full stops, because Cumulus MX always expects periods/full stops in .ini files regardless of the locale in use. Look up the individual .ini files in this Wiki as there are a few lines where the representation of a date is different between Cumulus 1 and Cumulus MX, so you should edit those lines for the files in your MX data folder.
* If you want to use your Cumulus 1 data folder with MX, and you use decimal commas in your Cumulus 1 data, you will need to edit the '.ini' files to change, in each stored value, the decimal commas into periods/full stops, because Cumulus MX always expects periods/full stops in .ini files regardless of the locale in use. In other respects the .ini files in the Cumulus 1 data folder can be read and used by MX, although MX when it needs to update these files will change the way dates are stored, see the Log File pages in the Wiki for more information.
* The '.txt' files in the data folder will work with both Cumulus 1 and MX - assuming you are using the same decimal and list separators in MX as you used in Cumulus 1 (i.e. the same locale).
* The '.txt' files in the data folder will work with both Cumulus 1 and MX - assuming you are using the same decimal and list separators in MX as you used in Cumulus 1 (i.e. the same locale).
* Any web tags on your web pages or in your scripts that use date and/or time formatting to change the default will need to be edited, and you may find this difficult because certain formatting characters (e.g. H or M) have different meanings when they appear in isolation in an output format to what they mean when combined with others (e.g.H:mm or 'd M'). See the [[Webtags]] page for full information on how to change these, and ask in the support forum if you have difficulty.
* Any web tags on your web pages or in your scripts that use date and/or time formatting to change the default will need to be edited, and you may find this difficult because certain formatting characters (e.g. H or M) have different meanings when they appear in isolation in an output format to what they mean when combined with others (e.g.H:mm or 'd M'). See the [[Webtags]] page for full information on how to change these, and ask in the support forum if you have difficulty.
* Your "Cumulus.ini" file must start with a capital letter for MX, and all the characters used within the configuration file must be within ASCII range, Cumulus 1 on Windows is not fussy about case in the file name. Cumulus MX adds further items to this file, but you do not need to change the contents of it for moving in either direction except in regards to the NOAA reports. Those from Cumulus 1 and MX are set up differently because of different codes to output a month format parameter as the change to date/time formats in webtags also applies to NOAA report file format lines in Cumulus.ini.  Also the [FTP site] section in Cumulus.ini will only work in MX with 'site' entirely in lower case, so if it is different in your copy, edit that.
* Your "Cumulus.ini" file must start with a capital letter for MX, and all the characters used within the configuration file must be within ASCII range, Cumulus 1 on Windows is not fussy about case in the file name. Cumulus MX adds further items to this file, but you do not need to change the contents of it for moving in either direction except in regards to the NOAA reports. Those from Cumulus 1 and MX are set up differently because of different codes to output a month format parameter as the change to date/time formats in webtags also applies to NOAA report file format lines in Cumulus.ini.  Also the [FTP site] section in Cumulus.ini will only work in MX with 'site' entirely in lower case, so if it is different in your copy, edit that.
*(Other file names within MX will be as supplied in the file that you download, or as Cumulus MX decides when it creates the file).  
*(Other file names within MX will be as supplied in the file that you download, or as Cumulus MX decides when it creates the file).  
* The settings in Cumulus 1 and MX work differently, for Cumulus 1 you choose to save changes by clicking OK, for MX changes are generally saved when you move on to next setting.
* The settings in Cumulus 1 and MX work differently, for Cumulus 1 you choose to save changes by clicking OK, for MX changes are either saved when you move on to next setting or when you click a '''Save''' button if one is provided.
Finally if you are moving from Windows to Linux, remember you need to learn a host of new commands!
Finally if you are moving from Windows to Linux, remember you need to learn a host of new commands!


5,838

edits