5,838
edits
Migrating from Cumulus 1 to MX: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Moving files from Cumulus 1 to MX
m (Text replacement - "Cumulus.ini" to "Cumulus.ini_(Cumulus_1)") |
|||
|
** MX [may] take some [settings from] interaction between the two [the specified locale and the default locale], and MX may struggle to read file [lines] created by Cumulus 1 if the MX locale is not precisely same as settings when that file [line was] created.
== Moving files from Cumulus 1 to MX beta==
There are some complications to take account if you try to use files created by the legacy Cumulus software when you swap to using MX, but that should not stop you migrating. It might mean that you choose to make your MX migration as an experiment, and maintain the ability to go back to the original Cumulus software until you are sure all your existing files have been transferred successfully.
===Configuration file===
It can be slightly confusing that the [[Cumulus.ini (Cumulus 1)|configuration file in the legacy Cumulus software]] has the same name as the [[Cumulus.ini|MX configuration file]], as although there is some consistency between many of the parameters in both, there are also some key differences (especially for later MX releases), and many parameters used by Cumulus 1 will be ignored by MX. Any ex Cumulus 1 main configuration file will gain a lot of new entries (that may upset Cumulus 1) once it has been processed by MX. In fact in your first run of MX you will have a lot of settings pages (on the admin interface) to work through to ensure all the new settings are correctly initialised.
If you are '''running MX on Windows''', filenames are not case sensitive, so MX will recognise "Cumulus.ini" or "cumulus.ini". But although Cumulus 1 might recognise "Cumulus1.ini" or anything else other than "Cumulus.ini". MX only recognises "Cumulus.ini". If you are planning on '''running MX on another device''', filenames are case sensitive, and your Cumulus 1 configuration file must be called "Cumulus.ini" with an initial capital followed by lower case, so it might need to be renamed.
====Examples of parameters that you might need to replace====
It is very difficult to list here which parameters you need to replace as it depends on your set-up. By set-up I mean which weather station type you use, which functionality within Cumulus you use, and which MX release you are installing. Thus treat what appears below as just examples, not a definitive guide.
If you use the standard trends web page:
*Replace: '''IncludeSTDImages=1''' (Cumulus 1) by ''IncludeGraphDataFiles=1'' (Cumulus MX) in [FTP site]
If your weather station uses a serial port type connection:
*Replace: '''Port=n''' (Cumulus 1) where n is a number, by ''ComportName=COMn'' (Cumulus MX on Windows) where the value is a string where n is same number, or replace by '''ComportName=/dev/ttyUSB0''' (CumulusMX on unix device) where the actual device name might need to be different if you have multiple USB ports.
If you use a RG11 rain gauge:
*Replace: '''RG11port=n''' and '''RG11port2 =n''' (Cumulus 1) where n is a number, by '''RG11portName=xxxx''' and '''RG11portName2=yyyy''' (Cumulus MX on Windows) where the value is a string with values as per previous paragraph depending on device on which Cumulus MX is running.
==== Parameters added ====
I cannot give you a definitive list here on what parameters are needed by MX that will not be in a configuration file created by the legacy Cumulus software, this is because it depends so much upon which version of MX you install when you move from Cumulus 1 (and which weather station type you use). A laborious way to discover what applies for you, is to work through all release announcements (starting at earliest in forum and ending at the release you have selected to install) for details. In the later MX releases, more and more of the parameters are set through web pages in the [[MX_Administrative_Interface#Changing_Settings|admin interface]] and so working through those pages will ensure all the extra parameters needed in the configuration file are set correctly for your installation. However in earlier MX releases, the web pages in that interface only include the "read-write" parameters, and there are many "read-only" parameters that need to be entered manually into the configuration file. Because this page was created when the latter applied, it is likely that information later on this page will be obsolete (unless someone has done the necessary updates).
===Compatibility for Data Log files===
*Steve Loft designed MX so that in general it was able to read [[
**See individual articles (accessed from that link) for more details on such differences.
**'''Please note, most of the information for MX here is taken from notes by Steve Loft, and so it applies to MX 3.0.0.'''
* If you move from Cumulus 1 to a version of MX up to 3.5.y, the transfer is likely to be significantly easier. This is because Steve Loft was keen to keep forward compatibility in his beta MX, and it took a while for Mark Crossley to revise the part of the MX code that reads log files.
** Cumulus 1 is tolerant of various separators for dates and times.
** It is difficult to move from Cumulus 1 to a release of MX that is 3.6.z or higher, mainly because you may find that Cumulus 1's .txt, and .ini, files can no longer be read.
**This is because '''for releases 3.7.0 onwards''', each log file in modern MX releases must have lines that match what is in the local settings absolutely perfectly;
**For Example: this means MX is now very fussy about the symbol that separates the 3 parts of a date, very fussy about decimal symbol, and expects the number of parameters/fields in files to be consistent with release 3.7.0.
**Thus modern releases are less tolerant of log files created by the original Cumulus software;
===Note for MX release 3.10.0===
This is when even more changes were made with regard to configuration settings, and has invalidated more of the documentation on this page. However, the author who created this page has not upgraded to later MX releases and is unable to update this page. When somebody else updates this page, this section should be updated to reflect the revised position.
===General points===
| |||
