Migrating from Cumulus 1 to MX: Difference between revisions

When Steve Loft designed Cumulus MX, he was able to learn from his experiences with both Cumulus 1 and Cumulus 2, so he decided to use dates to an ISO specification (ISO 8601 Data elements and interchange formats – Information interchange – Representation of dates and times), but in the local time zone of the particular user, and therefore log files are not [https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=15167 backwards compatible].   

MX (except early releases) reads the whole of this file as it starts running, so all lines must use exactly the same format.  

For MX (from release 3.5.4 onwards), the date separator specified for the locale when you run MX must be used in all lines of this file.  Please see [[Amending_dayfile#Date_Separator_in_MX]] for more detail of what MX expects.

It is all a bit technical, if MX expects "/", but you have "-" in some older lines. The complication comes because "-" may be used in value fields too, so you need to find a way of specifying a minus with two digits before it and two digits after it. For this correction you need to select '''Regular expression''' and then set  '''Find what''' to "^([\d]{2})-([\d]{2})-" and '''Replace with''' to "$1/$2/".  Please check this, as this was copied from a forum post by Mark Crossley and I have not verified it.

The dayfile.txt contains time-stamps following any value that represents a highest or lowest in the day.

MX will only accept colon ":" separator, all dayfile.txt time-stamps must be in "HH:mm" format.  You will need to edit your old lines if any use a different separator.

If you moved your Cumulus 1 installation from one windows pc to another, it is just possible that you might have a mix of "decimal comma" and "decimal point" in your values, or you might have changed the field separator (normally ";" or ",").  Again, these must be consistent in all dayfile.txt lines for MX, and must match what is defined in the locale used.