Cumulus MX FAQ: Difference between revisions

Cumulus MX FAQ (view source)

Revision as of 12:37, 28 March 2020

236 bytes added , 12:37, 28 March 2020

m

no edit summary

Sfws

5,838

edits

@@ Line 3: / Line 3: @@
 '''<big>Some of the following is out of date''', it refers to the original beta versions of MX not the latest release, other parts are just hints of what needs to be said ... <big>'''ANY volunteers to UPDATE THIS'''</big>?</big>'''
-There is a third party offering for helping you start and stop Cumulus MX  [https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767 on a Raspberry Pi]. There are two other related threads initiated by same author (Jank).
+'''It needs rewriting to be proper question and answer layout'''.
-One problem various people have had is swapping from a Windows environment to a Linux environment. There are lots of new commands to learn, and specifying the interface is different so getting MX to connect to your weather station has been a problem for some.
-For setting up your web site see [[website_setup|this page first]].
-There is no guide yet to the MX setting pages. Generally any edit you make to a setting takes effect as soon as you move to next setting, but some only take effect when you next restart Cumulus MX.  Most settings have a friendlier interface than the settings for the similar feature in Cumulus 1.
-Cumulus MX supports updating to secure web sites, this feature is not yet properly documented.
-The use of decimal comma gives rise to various problems mentioned in the forum, as the guidance above says Cumulus MX uses procedures that depend on full stops being used for the decimal point in many log files.
-There is confusion between Cumulus 1 symbols for minutes (nn) and the Cumulus MX symbol for minutes (mm) which Cumulus 1 uses to represent months (mm or MM allowed). This is seen in NOAA report names and any web tags that have had a date-time modifier added.
-On Cumulus 1, some people used '.' to separate the hours and minutes (HH.nn), this causes problems in MX that only accepts a colon separator (HH:mm). Thus files like the alltime.ini might have a mix of times in different formats.
-Another issue raised from time to time in the forum is that if you swap from Cumulus 1 to MX it does not access the old NOAA reports (because the settings in MX were not set to generate same file naming as previously used in Cumulus 1).
-Certain versions of Mono give problems, for example the Mono version 5 release has thrown up an issue with some locales and the short month names having an extra decimal point that Cumulus MX cannot cope with. Most of these problems are raised in the forum.
+*There is a third party offering for helping you start and stop Cumulus MX  [https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767 on a Raspberry Pi]. There are two other related threads initiated by same author (Jank).
+*One problem various people have had is swapping from a Windows environment to a Linux environment. There are lots of new commands to learn, and specifying the interface is different so getting MX to connect to your weather station has been a problem for some.
+*For setting up your web site see [[website_setup|this page first]].
+*For a guide to the settings pages of MX user interface see [[Cumulus_MX#Changing_Settings|here]].
+*Cumulus MX supports updating to secure web sites, this feature is not yet properly documented.
+*The use of decimal comma gives rise to various problems mentioned in the forum, as the guidance above says Cumulus MX uses procedures that depend on full stops being used for the decimal point in many log files.
+*There is confusion between Cumulus 1 symbols for months (mm or MM allowed) and the MX use of those symbols (mm means minutes, only MM is valid for months). If you used Cumulus 1 and set up NOAA report names using 'mm' instead of 'MM', then you have a problem in MX. Another issue raised from time to time in the forum is that if you swap from Cumulus 1 to MX it may not access the old NOAA reports if the settings in MX are set to generate different file naming to that previously used in Cumulus 1).
+*Similar problems occur for those swapping from Cumulus 1 to MX if they have used any web tags that have had a date-time modifier added. Here not only do you need to be careful whether you are using the right case, but also be prepared for single modifiers on their own to have a different meaning to when that modifier appears with other modifiers.
+*On Cumulus 1, some people used '.' to separate the hours and minutes (HH.nn), this causes problems in MX that only accepts a colon separator (HH:mm). Thus files like the alltime.ini might have a mix of times in different formats.
+*Certain versions of Mono give problems with some locales, for example the Mono version 5 release has thrown up an issue with some locales and the short month names having an extra decimal point that Cumulus MX cannot cope with. Most of these problems are raised in the forum.
 *If you want to use your Cumulus 1 data with MX, and you use decimal commas, you will need to edit the .ini files to change the decimal commas into periods/full stops. The other data files will be OK.
 *If you are trying to use your Cumulus.ini file from Cumulus 1, you will need to make sure it doesn't contain any non-ASCII characters