5,838
edits
Cumulus.ini (preserving history): Difference between revisions
Cumulus.ini (preserving history) (view source)
Revision as of 07:05, 17 May 2021
, 07:05, 17 May 2021→The Cumulus.ini file
m (→Ecowittt GW1000 Settings: column width) |
|||
| Line 28: | Line 28: | ||
When MX is restarted, it reads the ''Cumulus.ini'' that now exists. The settings it finds tell it what options you have selected and which sections of the MX code apply for your selections of weather station type (input) and for your selections of what processing it should do, and where you want it to send weather data to (output). | When MX is restarted, it reads the ''Cumulus.ini'' that now exists. The settings it finds tell it what options you have selected and which sections of the MX code apply for your selections of weather station type (input) and for your selections of what processing it should do, and where you want it to send weather data to (output). | ||
==File contents== | |||
The file is a simple text file. It is divided into sections with section names in square brackets (e.g. [Station]). These sections can appear in any order, by default new sections are appended after all previous sections. | The file is a simple text file. It is divided into sections with section names in square brackets (e.g. [Station]). These sections can appear in any order, by default new sections are appended after all previous sections. | ||
Within each section, there are parameters. Each parameter is in format '''Attribute=Value''', and appears on a line to itself. The parameters, within a section, can be in any order, by default new parameters are appended at end of the relevant section. | Within each section, there are parameters. Each parameter is in format '''Attribute=Value''', and appears on a line to itself. The parameters, within a section, can be in any order, by default new parameters are appended at end of the relevant section. | ||
== Add new parameters to file== | |||
If a new release of MX adds new parameters, then they will be automatically added to Cumulus.ini when you access that setting. | If a new release of MX adds new parameters, then they will be automatically added to Cumulus.ini when you access that setting. | ||
Some parameters have a default value, and you need to find the appropriate setting to change that value. However, others have an initial illegal value, and you are forced to give these parameter a valid setting before MX will allow you to save settings (and these "missing" values will stop MX doing any weather data processing). | Some parameters have a default value, and you need to find the appropriate setting to change that value. However, others have an initial illegal value, and you are forced to give these parameter a valid setting before MX will allow you to save settings (and these "missing" values will stop MX doing any weather data processing). | ||
==Remove redundant parameters from file== | |||
If you have been using Cumulus for a while, there might be parameters that are now obsolete, and newer parameters appended at end might make the file look strange. You can start afresh with a new file while Cumulus MX running... | |||
# Rename your Cumulus.ini to say Cumulus.ini.SAVE | |||
# In Cumulus go to one of the settings screens - say Alarms - and click the Update Alarms button | |||
# Cumulus should create a brand new Cumulus.ini file, | |||
#This will have all the settings you have chosen | |||
#They will now be in the order MX is expecting | |||
#Any redundant MX (or legacy Cumulus) settings will be removed. | |||
This tends to reorder the FTP settings section the most as it has 100 "entries" to save each with several settings, and some more recently added so they get appended out of order at the end | |||
=The settings pages in admin interface= | =The settings pages in admin interface= | ||