FAQ: Difference between revisions

674 bytes added ,  5 June 2020
m
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 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 useradministrative interface. thatThe canlatter beis viewed on a browser ''on any device connected to the same local network'' as the device that runs the engine. (forOn keythis securityadmin reasonsinterface thisyou userchange interfacesettings, shouldyou notcan beedit exposedthe overvarious logs, and you can view a series of web pages that allow you to see all the widerweather derivatives output from internet)MX.
* The settings for both Cumulus 1 and MX are held in [[Cumulus.ini|'''Cumulus.ini''']]. For MX the file name is case sensitive and must have capitals where shown.
* 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 case sensitivity of MX also applies to the section names within the file e.g. [FTP site] must use capitals for the FTP and must use lower case for site. Edit any section names that do not follow format in the wiki article for this file referenced above.
* 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).
**All the characters used within this configuration file must be within ASCII range (represented by binary 0 to 127, basically A to Z, a to z, 0 to 9, and some punctuation), any extended characters (such as those used for accented characters, symbols and non English characters) must be removed.
* 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.
**Whilst many settings are common between both flavours, some are not used by MX and MX has some new ones. In particular if you used '''Port''' in Cumulus 1, that will not be carried across to MX, and you will need to set '''ComPort''' instead. You are advised to check all '''Settings''' using the MX admin interface.
* 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.
*The contents of your Cumulus 1 '''Reports''' folder (NOAA style reports) can be read by MX.
*The contents of your Cumulus 1 '''data''' folder (log files ending with extension '''.ini''' or '''.txt''') can be read by MX.
**However, if you use decimal commas in your Cumulus 1 '.ini' files then you do need to change, in each stored value, the decimal commas into periods/full stops.
**MX when it needs to update these files will change the way dates are stored, see the [[:Category:Log Files|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 Cumulus 1 web templates (files using web tags) will not work with MX (whether you use the standard files provided or have written your own replacements)
**The Anyreason webis tagsbecause onthe yourcontent webof pagesthe orstandard inweb yourpages scriptsis thatdifferent. useFor dateany and/orweb timetemplates formattingyou tohave changewritten, the defaultyou will almost certainly need to bechange editedsome web tags, 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.
*(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 eitheronly saved when you move on to next setting or when you click a '''Save''' button if one is provided. If there is no Save button anywhere on the screen (as in Extra Web Files) then the setting is saved when you move to next field/line.
Finally if you are moving from Windows to Linux, remember you need to learn a host of new commands!
 
5,838

edits