5,838
edits
Compare C1 and MX: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
→Enhancements during Beta stage for MX and after MX came out of beta
m (→Introduction: typo) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 132: | Line 132: | ||
These two templates are totally different between flavours, this is because Cumulus generates locally some images containing graphs and gauges, then uploads those images, in constrast MX generates files containing data, that it can optionally upload so that the web page then uses that data to draw charts or gauges. | These two templates are totally different between flavours, this is because Cumulus generates locally some images containing graphs and gauges, then uploads those images, in constrast MX generates files containing data, that it can optionally upload so that the web page then uses that data to draw charts or gauges. | ||
= Key differences and similarities between Cumulus 1 and MX = | |||
NOTE: This section is also based on Steve Loft's wording taken from the support forum with minimal alteration for its new context. | |||
* 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 administrative interface. The latter is viewed on a browser ''on any device connected to the same local network'' as the device that runs the engine. On this admin interface you change settings, you can edit the various logs, and you can view a series of web pages that allow you to see all the weather derivatives output from MX. | |||
* The settings for both Cumulus 1 and MX are held in [[Cumulus.ini|'''Cumulus.ini''']]. For MX the file name is case sensitive [on non-Windows devices] and must have capitals where shown. | |||
**The case sensitivity of MX [on all devices, even Windows,] 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. | |||
**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. | |||
**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. | |||
*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 reason is because the content of the standard web pages is different. For any web templates you have written, you will almost certainly need to change some 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 zip 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 only saved 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! | |||
= Enhancements during Beta stage for MX and after MX came out of beta = | |||
While MX was in beta, there was limited documentation about what features were included and why, there was some fault reporting and a tracking list that showed when some of those issues were fixed, also initially the documentation on how MX had implemented features it did have was very sparse. The lack of a list of features in Cumulus 1, meant it remains difficult to track which Cumulus 1 features are or are not implemented in MX. Steve Loft said parts of MX were simply machine code level copies of parts of Cumulus 1 functionality, and parts were trying to offer better functionality, but he never said what was included in these two categories. | |||
There was a list of enhancements requested by users for Cumulus 1, but that list was deleted before work on MX started. Despite that, it does seem that some features that were on the now lost list of enhancements for Cumulus 1 that never got implemented in Cumulus 1, have been implemented in MX, although again there is no definitive documentation. | |||
The documentation that does exist is the release notes issued by Steve or Mark. In the next few sections, an attempt is made to prećis such announcements to track when the basic functionality from Cumulus 1 made it into MX. | |||
Of course weather station design evolves, and the sensors available vary. Thus another feature of MX development is adapting to new weather station dongles and new sensors (which obviously cannot be added to Cumulus 1). Once MX came out of beta, the changes in each release are being tracked in another [[Cumulus_MX_formal_release_versions|article]]. Obviously, you still need to look at the support forum for the detailed information in full release announcements about fixes, functionality changes, and actions needed to update to new major versions. | |||
== Version 3.0.x == | |||
build 3023 - you can now control the output format of <#tomorrowdaylength> using an entry in strings.ini like this example: | |||
[Solar] | |||
MoreDaylightTomorrow=Il y aura {0} minutes {1} secondes plus la lumière du jour demain | |||
LessDaylightTomorrow=Il y aura {0} minutes {1} secondes moins la lumière du jour demain | |||
Build 3025 - new MySQL (6 options) and custom HTTP uploads (can invoke a PHP script) facilities | |||
Also introduces a second pass to read archive records in catch up for Davis stations only | |||
Debug logging, diagnostic data logging, and ftp logging can now be set in the UI | |||
Changes for reading from Fine Offset and Davis stations | |||
Improved console messages at start up to indicate whether station has been connected successfully | |||
Makes sure dayfile.txt entry is always logged to MXdiags to help in case has problems writing file | |||
'Stop second instance' option now implemented (there were problems with this, see later versions) | |||
Graph periods can now be configured | |||
build 3035 - archives the month.ini and year.ini file at the end of the month/year as monthYYYYMM.ini and yearYYYY.ini. | |||
Build 3041 - Support for FTP over SSL/TLS (FTPS) - enable in Internet Settings | |||
build 3046 - added weather diary database (Note the MX diary file is different to the Cumulus 1 diary file). | |||
build 3047 - Web token parser updated to cope with html tag characters "<>" in the format string (see web tag page). | |||
build 3049 - This build enables ability to upload data to Windy.com. | |||
== Version 3.1.1== | |||
This release is mainly part of my attempts to add some of the Cumulus 1 features that are missing from CMX. | |||
build 3054 - Adds a Current Conditions editor and an All Time Records editor to admin interface | |||
Build 3056 - Fix for the All Time Records editor | |||
== Version 3.2.5== | |||
adds editors for files that track extremes previously missing from MX | |||
Build 3061 - that completes all the missing record editors from Cumulus 1 | |||
== Version 3.4.0== | |||
The big change for this release is adding historic data "catch-up" for Davis WeatherLink Live devices. | |||
Build 3064 - fixes bug in Monthly Records editor for dry/wet periods. | |||
==Version 3.4.5== | |||
This release continues attempts to add some of the Cumulus 1 features that are missing from CMX. | |||
Build 3069 - Adds Editors for: Dayfile, Monthly Logs, Extra Logs | |||
== Version 3.5.0== | |||
adds the generation of a Moon phase image, and the ability to push data to MQTT brokers. | |||
== Version 3.5.4 == | |||
Adds "Feel like temperature" as alternative to "apparent temperature" | |||
==From 3.7.0 onwards== | |||
Focus is now on adding new functionality. | |||
[[Category:Cumulus 1]][[Category:Cumulus MX]] | [[Category:Cumulus 1]][[Category:Cumulus MX]] | ||
