Migrating from Cumulus 1 to MX: Difference between revisions

m
no edit summary
mNo edit summary
Line 301: Line 301:
Do remember that with Cumulus 1 on Windows, each line in every file ends with both carriage return and line feed. If you are moving to MX on a Mac, each line should end with just a Carriage Return. For all Unix-based operating systems (Linux, Raspberry Pi OS, and other variants), each line should end with just a Line Feed. There are various editing tools that can do the necessary modification of all lines for you in just a couple of clicks; one such tool is Notepad++ (which although mostly used on PCs, can be used in other operating systems).
Do remember that with Cumulus 1 on Windows, each line in every file ends with both carriage return and line feed. If you are moving to MX on a Mac, each line should end with just a Carriage Return. For all Unix-based operating systems (Linux, Raspberry Pi OS, and other variants), each line should end with just a Line Feed. There are various editing tools that can do the necessary modification of all lines for you in just a couple of clicks; one such tool is Notepad++ (which although mostly used on PCs, can be used in other operating systems).


===Cumulus.ini_(Cumulus_1)===
===Cumulus.ini (trying to use your Cumulus_1 version)===


If you are running MX on Windows, filenames are not case sensitive, so MX will recognise "Cumulus.ini_(Cumulus_1)" or "cumulus.ini".  But although Cumulus 1 might recognise "Cumulus1.ini" or anything else other than "Cumulus.ini_(Cumulus_1)", MX only recognises "Cumulus.ini_(Cumulus_1)".
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_(Cumulus_1)" with an initial capital followed by lower case, so it might need to be renamed.
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_(Cumulus_1)" with an initial capital followed by lower case, so it might need to be renamed.


If you read the [[Cumulus.ini_(Cumulus_1)]] article, you will see that some parameters in the configuration file are only used by Cumulus 1, some only by MX, and some apply to both. MX will ignore any Cumulus 1 parameters it does not recognise, so you don't need to edit out lines. MX will also add any parameters it needs as read/write parameters for its settings, so in general you do not need to add them manually, you can simply set them using the relevant page in the settings part of the admin interface. There are of course a number of read-only parameters (these are ones that are entered directly into the configuration file and cannot be edited using settings), and there are some of these that are Cumulus 1 only and some that need to be added manually if you want to change the default.
If you compare the [[Cumulus.ini_(Cumulus_1)]] and [[Cumulus.ini]] pages, you will see that some parameters in the configuration file are only used by Cumulus 1, some only by MX, and some apply to both. MX will ignore any Cumulus 1 parameters it does not recognise, so you don't need to edit out lines. MX will also add any parameters it needs as read/write parameters for its settings, so in general you do not need to add them manually, you can simply set them using the relevant page in the settings part of the admin interface. There are of course a number of read-only parameters (these are ones that are entered directly into the configuration file and cannot be edited using settings), and there are some of these that are Cumulus 1 only and some that need to be added manually if you want to change the default.
 
There are a few exceptions to the above paragraph, if you look at [[Cumulus.ini_(Cumulus_1)#Parameters_changed]] you will see the list of a few parameters that '''may need to be changed''' in this configuration file (it depends on what type of weather station you use). But you don't need to look them up as they are also mentioned in next 2 sections (station settings and web pages) below.


There are also some differences in how some parameters in this file are used in the 2 flavours.
There are also some differences in how some parameters in this file are used in the 2 flavours.
Line 316: Line 314:


It is advised that you work through all the MX settings screens once you have the [[MX Administrative Interface|Admin interface]] working, ensuring they do represent how you want MX to work.  Some of the settings are for functionality you did not have in Cumulus 1 versions, and for these you will need to look up the link earlier in this sub-section.
It is advised that you work through all the MX settings screens once you have the [[MX Administrative Interface|Admin interface]] working, ensuring they do represent how you want MX to work.  Some of the settings are for functionality you did not have in Cumulus 1 versions, and for these you will need to look up the link earlier in this sub-section.
For the read-only settings in Cumulus.ini_(Cumulus_1), you may need to read the documentation in the forum.  The Cumulus.ini_(Cumulus_1) article in this wiki has had read-only parameters added to it now, but it is impossible to know if all have been covered there.


== Station connections==
== Station connections==
5,838

edits