Please note this page was created 13 June 2021.

At last update, it shows position as at beta build 3135, (missing some changes for the 3.12.0 release build of 3141).

This new page was created to reflect parameters added to Cumulus.ini in releases 3.8.0, 3.9.2, 3.10.0, and 3.12.0 (early beta builds - June 2021). It excludes all parameters removed after release 3.7.0.

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

Since this page describes a file whose content frequently changes, this page may be out of date, unless somebody bothers to update it for every change.

Purpose of Cumulus.ini file

This is a text file containing initialization parameters. This page covers those used by the Cumulus MX software application.

For MX there can only to be one Cumulus.ini file, and it must be stored in the same folder as the executable "CumulusMX.exe".

The configuration settings in Cumulus.ini have the following main purposes (this list may be incomplete):

Identify which weather station type MX is to read, and settings related to that model
Identify which derivatives are source ones (read directly from weather station and converted to your preferred units) and which derivatives MX is to calculate for you.
Identify where you want MX to output to (options include external web sites, and database tables)
Control what is output to those destinations, to the extent that each can be configured

Why does this Wiki now contain multiple pages describing "Cumulus.ini"?

MX has been developed very dramatically by Mark Crossley:

There were minor differences between the legacy cumulus.ini (for versions 1.x.y, ending with 1.9.4) with documentation now here and the original 3.0.0 beta (previously documented on Cumulus.ini (Beta) page, but that page has been cleared)
The dramatic development of MX produced considerable differences between that original MX beta, and the configuration that applied up to 3.7.0, as now documented here
Even more dramatic changes to the MX configuration have been happening since 3.8.0, with the biggest changes at 3.9.2, 3.10.0, and 3.12.0; therefore, the decision was taken to abandon maintaining the page previously called "Cumulus.ini", and start again with a brand new empty page!

All the pages, previously called "Cumulus.ini", can be found from the owning category. The original page was preserved at Cumulus.ini_(preserving_history) so look there for its editing history. That page also expands on the above summary of why that old page was replaced by this new page.

Need to install MX 3.12.0

If you are using Cumulus 1 or a release of MX earlier than 3.12.0, be aware that the content of "Cumulus.ini" is totally different to the file for later MX releases. (It might have been better had the file been given a new name in release 3.12.0).

The way the developer decided to implement it, is that when somebody installs release 3.12.0, any existing "Cumulus.ini" file is renamed, and a new "Cumulus.ini" file is created from scratch, and from then onwards all changes apply to the new file. As 3.12.0 is the only release that can create the replacement file, it is highly recommended that anybody currently using an older release, downloads 3.12.0 from here and runs that release for a while before upgrading to the latest release here.

Simplifications

The MX configuration is very different to that used by the legacy software. MX has far more optional functionality than the legacy software, therefore MX requires far more parameters to tailor all these functionality options.

The file is read into Internal Variables as Cumulus starts, and those variables are written back into the file when any settings are changed.

In the MX releases covered by this Wiki page, almost all settings are edited from a number of web pages for settings included in the local web interface.

To make it easier for the Cumulus MX user, the developer had to devise a way to make it easier to quickly assign the settings that might be best for those new to Cumulus to get the software working without needing to understand all the settings. This is achieved by introducing some "master" settings, these both determine which dependent settings are displayed, and what default values those dependent settings take. So a novice just has to get the "master" settings right and they then achieve a typical way of using that functionality! For those who are slightly more expert, full flexibility is available by adjusting the majority of dependent settings to what is required for more specialised requirements.

The ongoing development of MX is focused on making configuration even simpler, by revising the pages for the setting of all parameters, and improving the labels/grouping. By moving away from legacy software terminology and the parameters it needed; the developer has started introducing parameters and labelling that fits the MX design.

It may be worth remembering why the legacy software made life complicated:

There could be more than one "cumulus.ini" file for the Legacy Cumulus up to 1.9.4, as explained here.
The vast majority of parameters (that could appear in the file) could only be edited directly in the file.
- To simplify the editing in-situ, the author (Steve Loft) recommended that, within any "File section" you intended to change, you sorted the parameters into alphabetical order, before editing the file.
- That advice was given because having parameters in alphabetical order would prevent you inserting a parameter that already existed.
- This would avoid the potential problem arising from the design that Cumulus 1 would ignore any duplicate parameter; (Cumulus would take the first one it found, and that might not be the last one you edited!)

Structure of Cumulus.ini

The file is divided into "File sections" (see terminology definitions below), each File section name is on a separate line (with no other content) and enclosed in square brackets (e.g. [Station]).

These File sections can appear in any order, by default new File sections are appended after all previous File sections, but if you prefer the File sections in another order, MX can still find them, although it may spend more time searching!

Within each File section, there are parameters. Each parameter is in format Attribute=Value, and appears on a line to itself.

The parameters, within a File section, can be in any order, by default new parameters are appended at end of the relevant File section.

How this Wiki page classifies settings

This new Wiki page is no longer designed around the way parameters appear in the file, as earlier pages with this name were. Here are some of the reasons:

Settings can appear in any order in the file, but it is easier to find them on this page if they are listed alphabetically
Releases might add new parameters, or remove old parameters, so looking at a file does not identify which parameters need to be explained on this page
Releases might add new sections in the file, or remove old sections in the file, so organising this page by those "File sections" no longer makes sense
The settings interface in MX is being comprehensively redesigned. That means this documentation cannot be organised by the way MX organises its settings pages.
- To clarify that reason, if this Wiki page was organised according to the Settings Screens that applied say at release 3.8.0, a different sequence might be required in say 3.12.0 because that changed the Settings Screens.

Some classification is still needed to help you the reader find settings, only you can judge whether the grouping here suits you! In creating this page, I have tried to think of a way to group various settings and arranged those groups alphabetically, to make navigation as easy as I can.

Of course if you have your own ideas of a better way to group the documentation here, you are welcome to implement your preference, by editing this page.

Tabular presentation

Within the groupings I have selected, individual settings are normally presented as rows in tables for clarity on this Wiki page. The individual tables can have up to 7 columns. The columns can explain for each setting:

Where in the admin interface you edit it (MX page and MX section in terminology below)
Whether the Setting is always shown on the Settings Page ("Always" is shown), or is only shown if an earlier Setting has a particular selection (dependency is shown)
What File Section (in terminology below) it appears in with the file (always appears, and is shown, between square brackets)
The attribute name used for the parameter in the file (always shown with an equals sign after it)
Which release introduced the setting(s)
What is the default value for the parameter, (and what that default value means)
A description of what the parameter represents, and what values it can take

If the content of any column would be same for every row, then that column is omitted, and the relevant information is instead stated before the table.

Exceptions to above table styling:

MQTT parameters are handled slightly differently, as they did not fit that standard layout
The mean temperatures, and normal rainfall figures, with one parameter per month, have been presented as text, rather than a table for simplicity
For the Extra Web Files Settings page, where the settings page uses editable grid software, instead of listing all 800 settings individually, the table here is split into just 8 rows, each of which applies to 100 parameters in the file.

Terminology used on this Wiki Page

Terminology	What it means
Qualifications: Settings page Wiki page	Because "page" could refer to either this page or the Settings page, page will always be qualified
Shown on Settings page?	Sometimes whether you see a particular setting on the Settings Page, depends on a previous selection has been made, that is explained under this heading
MX Section	Under this heading you will find how to navigate to the relevant setting within the admin interface. This covers the page where you edit the setting, followed by →, and then the section (and sub-section where relevant) that you have to select to see the setting Each MX section on the Settings page has to be opened individually (by either a button for maximum accessibility, or a Click ▶to expand, click ▼ to collapse for alternative styling).
Label on Settings page	Under this heading you will discover how MX labels the individual setting where you edit that setting
File Section	Within the file, a number of section headings are used, to gather multiple parameters together. Thus under this heading, for each setting, the table shows the File Section where the parameter will be stored
Parameter Line Entry	Within the file each setting is represented by a parameter in format attribute=value on a line to itself without any punctuation symbols. If the parameter has a default value, that is shown here and explained in next column
Default	This is the value (if any) that the individual setting takes when it has not been amended. Some parameters do not have a default value and "(none)" will be shown in this case. No brackets surround literal text representing default value, which is normally also seen in Parameter Line Entry. In general, round brackets are used in Default column to indicate an explanation.
Description	Under this heading you will find an explanation of the setting including (where relevant) what values it can take

When, and How, does MX read the Configuration File?

Whenever MX is restarted, it reads the latest Cumulus.ini and if it exists strings.ini (briefly mentioned below); from these one (or two) file(s), it learns the configuration that you want it to use.

Essentially, MX reads the whole file, for each attribute part of a parameter in the file, there is a variable stored within the MX code. So the value part of each parameter is assigned to the respective variable. Hence MX will not permit any duplicates for any parameter. If MX finds a parameter it does not understand, it ignores that parameter.

This means a Cumulus.ini file created by the legacy software, or by an old release of MX, can still be read by the current release of MX, as it just ignores all the obsolete parameters. However, since MX now has a lot of new parameters in the file, that were not in the legacy file, nor in a file created by an early MX release, it is often easier to start again with a new configuration file, as explained later, to ensure the configuration of MX is correct for you.

MX also creates a backup copy of "Cumulus.ini" in a sub-folder of Backup folder that is named according to current date and time.

What MX finds in your "Cumulus.ini" does of course determine what you see when you open any of the Settings pages, in the admin interface. This is because the displaying of some settings is dependent on another setting.

For completeness I mention here, configuration information for MX can also be stored in an optional file strings.ini, that is used to identify how various standard output phrases are to be modified to suit you.

Settings Configuration for MX

The MX software offers much functionality and flexibility. Consequently, it has an extensive set of configuration settings, fortunately apart from the initial settings of model and units (see next sub-section), recent releases have simplified many of the settings for optional features by providing particular selections to affect a whole range of others (for predicted uses), instead of forcing you to individually work through every individual setting.

Please see First Run of MX for how to set up settings when you first use MX.

What happens if I upgrade MX?

If you upgrade to a newer MX build, as that release distribution does not contain a "Cumulus.ini", you cannot lose your settings entered in your existing file. However, be aware that a new release may remove some settings, and add new settings, hopefully the release announcement will give specific details. Otherwise, you will need to work through all the Settings Pages, and all the "MX Sections" (see Terminolgy above)

Where do I change settings?

The current design of MX expects that Cumulus Users will never need to edit the "Cumulus.ini" file directly, as there are a number of settings pages in the admin interface and users are expected to use those Settings pages to amend the individual MX settings.

Please see MX_Administrative_Interface#Changing_Settings for basic information, including how to load the admin interface (sometimes called the "dashboard interface" or "user interface").

Furthermore, at the end of each (meteorological) day, MX creates a back-up in the backup/daily/TIME_NAME sub- folder. The TIME_NAME is constructed from a string of digits representing the date and time the directory was created (without any punctuation) e.g. 20060519090000. In that folder, recent MX releases, include a copy of the current "Cumulus.ini" file.

Do I need to restart MX?

If you change a setting directly in the file, you must stop MX beforehand. The setting takes effect when you restart MX.

If you change a setting, using the admin interface, it may, or may not, take effect immediately...

The settings available on the various pages in the admin interface fall into two groups:

SETTINGS THAT TAKE EFFECT IMMEDIATELY ON CLICKING “SAVE”
SETTINGS THAT ONLY TAKE EFFECT WHEN MX IS RESTARTED

There used to be a third group. Before Release 3.11.2 - build 3131 a few changes made in the interface were not saved into "Cumulus.ini", and those few settings were therefore lost when MX was restarted. One example of these former exceptions was that the former action selecting adding extra debugging information to file in MXDiags folder was previously not saved for subsequent session.

For the current MX release, any change made (on any settings page) will be saved into "Cumulus.ini", and will still apply when MX is restarted. That restart will ensure all settings changed in the last session do take effect, even those that did not take effect before the restart.

Unfortunately, there is no documentation available from developer on which settings, at any release, do not take effect until MX is restarted. We do know that you need to do a restart after choosing the station model, and that is unlikely to change.

In early MX releases most configuration settings required a restart of MX before they took effect, but since then in some releases, certain settings that used to require a restart have been changed so they take effect intermediately. It is anticipated, as MX develops, the majority of settings will become ones that take effect without a restart of MX.

This means that any attempt to document here which changes do require a restart of MX is working against a moving target. Consequently, this documentation does not indicate where a restart is required. You can either play safe, and restart MX each time you finish making edits to settings, or you can read all the support forum announcements, and see if you can find any information about whether a restart is needed, for whatever particular settings you are changing, at the release you are using.

How to Remove Redundant parameters from file

If you have been using Cumulus for a while, there might be parameters that are now obsolete left in your configuration file.

MX will ignore any parameters that it no longer recognises, but there is a simple way to make MX create a new file for you, keeping your existing settings, but ensuring the new file does not have any obsolete parameters.

The following procedure is best done after, not before, you upgrade MX, as installing a new release might add/remove parameters to/from "Cumulus.ini".

Apart from that upgrade consideration, you can start afresh with a new file anytime by following this very simple procedure:

You must do this while keeping Cumulus MX running (to preserve existing settings)...

Rename your existing Cumulus.ini to say Cumulus.ini.sav (this keeps the file, but stops MX finding it)
In Cumulus go to one of the settings screens, (e.g. Program Settings which is currently a short page) – simply click ‘’’Save Settings’’ (i.e. any action that makes MX save settings to its configuration file)
- It is possible this might highlight a new parameter that does not yet have a valid value (e.g. the Alarm settings page, which uses ‘’’Enable Alarms’’’ rather than "Save settings", got extra settings without defaults at 3.11.0).
Cumulus (if it accepts that save) will now 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
- MX default sort order is from where entries are set in the code, and that is far from alphabetic!
As MX is unaware of settings it used previously, but does not use now, (and MX is unaware of what settings the legacy software used), it won’t write back any redundant settings in the new configuration file.

As well as changing the order in which parameters are stored, this re-generation may show up other changes (if you do have reason to examine the new file and compare with the old file):

A major change is likely in the '''[Station]''' section as that has seen a lot of changes as MX is developed.
The ’’’[Graphs]]’’’ section has also seen a number of changes as MX has developed.
The most dramatic change may happen in '''[FTP Site]''' as any reorganisations to the list of parameters for Extra Web Files are reproduced 100 times.

Editing the file directly

At the time of writing this, the work to code up MX settings pages is not yet completed.

So the Settings Pages could not modify all the parameters, that can appear in the file and get used by MX. Therefore, there were still some settings that could only be amended by stopping MX, then editing the relevant parameter in the file directly, before restarting MX.

However, it is likely that in a few releases time, there will be no necessity to directly edit the file.

That said, working through the various settings pages, and all the options (often within multiple MX sections) can be laborious. Consequently, those with some understanding of the file contents may still wish to make some changes with MX stopped, by editing the file. The only caution that needs to be stressed is "be careful"; as this editing the file directly bypasses any validation that is done when using the Settings Pages, and so might result in an inconsistent set of parameters, and (in the worse case) perhaps a software crash.

An example of why you might edit file instead of using Settings Page

If (for example) you find the Extra Web Files editor hard to use, you might decide to stop Cumulus MX and still edit this configuration file directly for changes to those parameters. Given that MX ignores any parameter it does not understand, while editing the file, you can temporary have old and new parameters in the file. All you need to do is prefix those parameters you don't want MX to use with any character you like before the "Extra" in the attribute name.

When MX adds new parameters to file

In theory, there is no reason why you should manually add any extra parameters directly into the file.

Since MX creates, and edits, the file, it should ensure all parameters it understands are in the file.

When this new page was being created, some of the parameters in the file that MX understands, could not be matched to any known setting in the Settings Interface pages, but it may be a future release will correct that.

If a new release of MX adds new parameters, then:

If the new parameter has a valid default value, MX will work perfectly using that default value.
- You won't need to know the parameter exists, unless you decide to change it, and find out what values it can take either in a drop-down on the relevant Settings page, or in the relevant table below.
Other new parameters may be given an initial illegal value, because MX cannot guess what value will work for you.
- This is to enforce the need to give these parameter a valid value before MX will allow you to save settings.
  - Sometimes, MX will not do any weather data processing, until these ‘’’missing’’’ values are edited.
  - In other cases, you might not realise that your file is missing one or more parameters, unless you go into the relevant Settings page, and find you can't save (Enable for Alarms page).

In practice, as already mentioned, there might be a parameter that you need to get MX working correctly for you, but have to add directly to the file as (at the release you are using) that setting has not yet been added to any Settings page.

Before this page actually lists all the settings I know of, let me give an example of a seting with a valid default, and an example of a setting that has an invalid default:

Example of new Parameter with valid default

When accessibility was added, its parameter defaulted to the old expand/contract sections design (see first table below).

You can, optionally, go into "Program Settings" or "Station Settings" pages, where you tick the box to get the (more accessibility friendly) selection button alternative.

Example of new Parameters with no valid initial value

As a specific example, release 3.11.0 added emailing capability; that requires quite a lot of new parameters to be added to the file. You could use MX without these new parameters, but the Alarm Settings page would not allow you to click Enable until you had defined various settings on another Settings page, as well as on this Alarm Settings page.

Tables listing Settings

Accessibility

Introduced Release 3.10.0 - build 3115
File Section is [Program]

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
EnableAccessibility=0	Two places where you can edit this setting: (Either) Program Settings → (First tick box) (Or) Station Settings → (First tick box)	Enable accessibility features	0 (disable)	Determines styling of settings pages: Set to 1 to make this (and other pages) appear in a button selection style (more friendly on an accessibility basis). Leave it at zero for a Click ▶to expand, click ▼ to collapse styling.

Alarms (and emails)

In the table below "Notify" determines whether an alarm is shown on the "Dashboard" page, for release 3.11.2 and subsequent the alarm also has to be enabled for it to appear.

Introduction column:

There was no alarm functionality in builds in the 3.0.0 and 3.1.x series
Any alarm functionality where the column says "Legacy Cumulus" was available before 1.9.0 and introduced into MX in one of the releases between 3.2.0 and 3.5.4.
Any alarm functionality where the column says "Cumulus 2" was requested for that withdrawn flavour, subsequently added to a 1.9.x release, introduced into MX in one of the releases between 3.2.0 and 3.5.4.
New alarm functionality introduced in the range of releases 3.2.0 to 3.5.4 has that range shown (rather than the exact release).
For alarm functionality first introduced in or after release 3.7.0, the release of introduction is shown in "Introduced" column.
There were no changes to Alarm functionality between 3.7.1 and 3.8.4 inclusive, so if you are running one of the 3.8.x releases, the Wiki page that applies for "alarms" is the early MX releases page, not this Wiki page.
In the range of releases subsequent to 3.9.0 as covered by this Wiki page, the alarm functionality has been dramatically changing:
- Latching of alarms was introduced at 3.9.1 (b. 3096), most alarms had no default for how long they stayed "latched", but at least one had a 12 hour default and at least one had an until end of day default.
- At 3.9.2 (b.3097) reporting of notifications were added to the admin interface (called "Cumulus Dashboard" in the relevant release announcement at Cumulus MX Announcements and Download - PLEASE READ FIRST,
- At 3.9.5 (b. 3100) the latching functionality was corected,
- At 3.9.6 (b.3101) the alarm latch hours were all defaulted to 24 hours,
- At 3.11.0 (build 3129) where the email functionality was added,
- And at 3.11.2 (b. 3131) where the release announcement says "this release sees the Alarms getting some more love".

"Shown on Settings page?" and "MX Section" columns:

For releases between 3.2.0 and 3.10.5, all alarm related settings were "always" shown, and none required opening a "MX section".
For release 3.11.0 and subsequent releases, the introduction of email functionality means there are now some alarm related settings on the "Internet Settings" page, where there is a section "Email Server Settings" that needs to be opened, and a master setting that determines whether other settings are shown or not.

"Label on Settings page" column:

For releases between 3.2.0 and 3.10.5, all alarm related settings were shown using a HTML table, so the entry in the label column in the table below quotes the text shown after the check box that starts the settings table row
For release 3.11.0 and subsequent releases, the introduction of email functionality means there are now some alarm related settings where the label column quotes the text shown beside the individual setting, but all other alarm related settings quote the text shown after the check box that starts a settings table row

Parameter Line Entry	Shown on Settings page?	File Section	Introduced	MX Section	Label on Settings page (mostly in Alarm column)	Default	Description
alarmhighgust=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Wind gust more than:	0 (disabled)	Use the spin button to select the Value of calculated (10 minute) wind gust that has to be exceeded to trigger the alarm
alarmhighpress=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure rises above:	0 (disabled)	Use the spin button to select the Value of measured Sea Level Pressure that has to be exceeded to trigger the alarm
alarmhighrainrate=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall rate rises above:	0 (disabled)	Use the spin button to select the Value of calculated rainfall rate that has to be exceeded to trigger the alarm
alarmhighraintoday=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall today more than:	0 (disabled)	Use the spin button to select the Value of calculated daily rainfall total that has to be exceeded to trigger the alarm
alarmhightemp=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature rises above:	0 (disabled)	Use the spin button to select the Value of measured outside temperature that has to be exceeded to trigger the alarm
alarmhighwind=	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Average wind more than:	0 (disabled)	Use the spin button to select the Value of calculated average wind speed that has to be exceeded to trigger the alarm
alarmlowpress=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure falls below:	0 (disabled)	Use the spin button to select the Value of measured Sea Level Pressure it must go below to trigger the alarm
alarmlowtemp=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature falls below:	0	Use the spin button to select the Value of measured outside temperature it must go below to trigger the alarm
alarmpresschange=0	(always)	[Alarms]	Cumulus 2	Alarm Settings	Pressure changes by:	0	Use the spin button to select the Value by which the measured Sea Level Pressure must rapidly change (in legacy Cumulus this was taking trend for the last hour, the developer has not specified what period applies for MX) to trigger the alarm
alarmtempchange=0	(always)	[Alarms]	Cumulus 2	Alarm Settings	Temperature changes by:	0	Use the spin button to select the Value by which the measured outside temperature must rapidly change (in legacy Cumulus this was taking trend for the last hour, the developer has not specified what period applies for MX) to trigger the alarm
BatteryLowAlarmEmail=	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Station batteries are low	(blank)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
BatteryLowAlarmLatch=	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Station batteries are low	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
BatteryLowAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Station batteries are low	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
BatteryLowAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Station batteries are low	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
BatteryLowAlarmSet=0	(always)	[Alarms]	(changed at 3.10.3)	Alarm Settings	Station batteries are low	0 (disabled)	If tick Enable, the alarm will be triggered if the weather station either supplies a voltage, or other battery indication that can be interpreted, and MX interprets that as indicating a low battery
BatteryLowAlarmSound=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Station batteries are low	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
BatteryLowAlarmSoundFile=alarm.mp3	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Station batteries are low	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
DataSpikeAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Data spike is detected	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
DataSpikeAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Data spike is detected	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
DataSpikeAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Data spike is detected	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
DataSpikeAlarmNotify=0	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data spike is detected	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
DataSpikeAlarmSet=0	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data spike is detected	0 (disabled)	If tick Enable, the alarm will be triggered if while MX is processing raw data from the weather station (in archive catch-up or normal running) there is a spike (a change since previous raw value read that exceeds a difference as defined on "Calibration Settings → Spike removal")
DataSpikeAlarmSound=0	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data spike is detected	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
DataSpikeAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data spike is detected	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
DataStoppedAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Data connection is lost	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
DataStoppedAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Data connection is lost	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
DataStoppedAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Data connection is lost	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
DataStoppedAlarmNotify=0	(always)	[Alarms]	Release 3.4.2	Alarm Settings	Data connection is lost	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
DataStoppedAlarmSet=0	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data connection is lost	0 (disabled)	If tick Enable, the alarm will be triggered if while MX is processing raw data from the weather station (in archive catch-up or normal running) there is a spike (a change since previous raw value read that exceeds a difference as defined on "Calibration Settings → Spike removal")
DataStoppedAlarmSound=0	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data connection is lost	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
DataStoppedAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Release 3.7.0	Alarm Settings	Data connection is lost	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
DestEmail=	(always)	[Alarms]	Release 3.11.0	Alarm Settings	To email adressess(es)	(blank)	Please note: You cannot Update Alarms to save any settings on this page if the text box for this parameter is left blank. You can enter either a single email addresss or a list of email addresses here, a semicolon must be used as separator between addresses.
Enabled=0	When section opened	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Enabled	Not ticked (shown as 0 in Cumulus.ini)	If you tick here, a selection of further options (identified by ^) are shown
FromEmail=	(always)	[Alarms]	Release 3.11.0	Alarm Settings	From email address	(blank)	Please note: You cannot Update Alarms to save any settings on this page if the text box for this parameter is left blank. You can enter a single email addresss
HighGustAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Wind gust more than:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighGustAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Wind gust more than:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighGustAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Wind gust more than:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighGustAlarmNotify=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Wind gust more than:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighGustAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Wind gust more than:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighGustAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Wind gust more than:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighGustAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Wind gust more than:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HighPressAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Pressure rises above:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighPressAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Pressure rises above:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighPressAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Pressure rises above:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighPressAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Pressure rises above:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighPressAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure rises above:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighPressAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure rises above:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighPressAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure rises above:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HighRainRateAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Rainfall rate rises above:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighRainRateAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Rainfall rate rises above:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighRainRateAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Rainfall rate rises above:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighRainRateAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Rainfall rate rises above:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighRainRateAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall rate rises above:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighRainRateAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall rate rises above:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighRainRateAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall rate rises above:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HighRainTodayAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Rainfall today more than:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighRainTodayAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Rainfall today more than:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighRainTodayAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Rainfall today more than:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighRainTodayAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Rainfall today more than:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighRainTodayAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall today more than:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighRainTodayAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall today more than:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighRainTodayAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Rainfall today more than:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HighTempAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Temperature rises above:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighTempAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Temperature rises above:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighTempAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Temperature rises above:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighTempAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Temperature rises above:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighTempAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature rises above:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighTempAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature rises above:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighTempAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature rises above:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HighWindAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Average wind more than:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if alarm is triggered
HighWindAlarmLatch=0	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Average wind more than:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HighWindAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Average wind more than:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HighWindAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Average wind more than:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HighWindAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Average wind more than:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HighWindAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Average wind more than:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HighWindAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Average wind more than:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HttpUploadAlarmEmail=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
HttpUploadAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
HttpUploadAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
HttpUploadAlarmNotify=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
HttpUploadAlarmSet=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
HttpUploadAlarmSound=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
HttpUploadAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
HttpUploadAlarmTriggerCount=1	(always)	[Alarms]	Release 3.11.2	Alarm Settings	HTTP upload errors	1 (trigger immediately a failure occurs)	Use the spin button to specify how many failures need to occur, within the latch time, before the alarm is triggered
Logging=0	^	[SMTP]	Release 3.11.2	Depends on release: (Release 3.9.4 to 3.11.4) Program Settings → Program General Options (Release 3.12.0 onwards) Program Settings → Logging Options	Email logging	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want to enable extra SMTP logging to the smtp.log file in the MXdiags folder. Don't tick (value shown as 0 in Cumulus.ini) for no extra information in diagnostic logging
LowPressAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Pressure falls below:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
LowPressAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Pressure falls below:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
LowPressAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Pressure falls below:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
LowPressAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Pressure falls below:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
LowPressAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure falls below:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
LowPressAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure falls below:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
LowPressAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure falls below:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
LowTempAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Temperature falls below:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
LowTempAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Temperature falls below:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
LowTempAlarmLatchHours=24	(always)	[Alarms]	Release 3.9.1	Alarm Settings	Temperature falls below:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
LowTempAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Temperature falls below:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
LowTempAlarmSet=1	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature falls below:	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
LowTempAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature falls below:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
At time of writing there is a MX bug: (Reads) LowTempAlarmSoundFile=alarm.mp3 (Writes) LowTempAlarm.SoundFile=alarm.mp3	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Temperature falls below:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
MySqlUploadAlarmEmail=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
MySqlUploadAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
MySqlUploadAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
MySqlUploadAlarmNotify=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
MySqlUploadAlarmSound=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
MySqlUploadAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
MySqlUploadAlarmTriggerCount=1	(always)	[Alarms]	Release 3.11.2	Alarm Settings	MySQL upload errors:	1 (trigger immediently a failure occurs)	Use the spin button to specify how many failures need to occur, within the latch time, before the alarm is triggered
Password=	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Password	(blank)	Text box where you enter password needed to authenticate with your SMTP email server
Port=587	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Network Port	587	Text box where you enter the port used to connect to your SMTP email server
PressChangeAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Pressure changes by:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
PressChangeAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Pressure changes by:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
PressChangeAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Pressure changes by:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
PressChangeAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Pressure changes by:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
PressChangeAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure changes by:	0 (disabled)	If tick Enable, the alarm will be triggered if measured Sea Level Pressure rapidly changes (in legacy Cumulus this was taking trend for the last hour, the developer has not specified what period applies for MX) by, or more than, the selected Value in earlier parameter
PressChangeAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Pressure changes by:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
PressChangeAlarmSoundFile=alarm.mp3	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Pressure changes by:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
RequiresAuthentication=0	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Use authentication	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if a user name and password is needed to authenticate with your SMTP email server Don't tick (value shown as 0 in Cumulus.ini) if your SMTP email server is not protected by a user name or password
SensorAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Sensor contact lost	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
SensorAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Sensor contact lost	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
SensorAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Sensor contact lost	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
SensorAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Sensor contact lost	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
SensorAlarmSet=1	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Sensor contact lost	0 (disabled)	If tick Enable, the alarm will be triggered if calculated (10 minute) wind gust exceeds the selected Value in earlier parameter
SensorAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Sensor contact lost	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
SensorAlarmSoundFile==alarm.mp3	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Sensor contact lost	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
ServerName=	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Server Name	(blank)	Text box where you enter name, or IP address of your SMTP email server
SSLOption=1	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Use SSL/TLS (deprecated Secure Sockets Layer and replacement Transport Layer Security)	1 (Auto)	Drop down: 0 = None 1 = Auto 2 = TLS on connect 3 = Start TLS 4 = Start TLS when available
SpikeAlarmTriggerCount=	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Data spike is detected	1 (trigger immediently a failure occurs)	Use the spin button to specify how many failures need to occur, within the latch time, before the alarm is triggered
TempChangeAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Temperature changes by:	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
TempChangeAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Temperature changes by:	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
TempChangeAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Temperature changes by:	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
TempChangeAlarmNotify=0	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Temperature changes by:	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
TempChangeAlarmSet=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature changes by:	0 (disabled)	If tick Enable, the alarm will be triggered if outside temperature rapidly changes (in legacy Cumulus this was taking trend for the last hour, the developer has not specified what period applies for MX) by, or more than, the selected Value in earlier parameter
TempChangeAlarmSound=0	(always)	[Alarms]	Legacy Cumulus	Alarm Settings	Temperature changes by:	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
TempChangeAlarmSoundFile=alarm.mp3	(always)	[Alarms]	within 3.2.0 to 3.5.4	Alarm Settings	Temperature changes by:	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
UpgradeAlarmEmail=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Cumulus upgrade available	0 (disabled)	If tick Email, and all the email settings marked ^ have been completed, an alarm will be sent if an HTTP upload fails
UpgradeAlarmLatch=0	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Cumulus upgrade available	0 (disabled)	If tick Latches, an alarm will be maintained (latched) for a user configurable number of hours (see next parameter)
UpgradeAlarmLatchHours=24	(always)	[Alarms]	Release 3.11.2	Alarm Settings	Cumulus upgrade available	24 (default set only since release 3.9.6)	Use the spin button to select the number of hours (specified in Latch h(ou)rs column) that the "latch" is maintained if previous setting is set to 1 (tick on settings page)
UpgradeAlarmNotify=0	(always)	[Alarms]	Release 3.9.3	Alarm Settings	Cumulus upgrade available	0 (disabled)	If tick 'Notify, MX will show the status of this alarm on the Dashboard page of the interface
UpgradeAlarmSet=0	(always)	[Alarms]	Release 3.9.3	Alarm Settings	Cumulus upgrade available	0 (disabled)	If tick Enable, the alarm will be triggered if outside temperature rapidly changes (in legacy Cumulus this was taking trend for the last hour, the developer has not specified what period applies for MX) by, or more than, the selected Value in earlier parameter
UpgradeAlarmSound=0	(always)	[Alarms]	Release ???	Alarm Settings	Cumulus upgrade available	0 (disabled)	If tick Play sound, if the alarm is triggered, then the file specified in next parameter will be played
UpgradeAlarmSoundFile=alarm.mp3	(always)	[Alarms]	Release ???	Alarm Settings	Cumulus upgrade available	alarm.mp3	Specify a file name for a music file stored in the CumulusMX\interface\sounds or CumulusMX/interface/sounds folder
UseHTML=0	(always)	[Alarms]	Release 3.11.0	Alarm Settings	Email uses HTML text formatting	0 (UTF-8 plain text)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you wish to use HTML encoding format for your customised emails Don't tick (value shown as 0 in Cumulus.ini) if you are happy to use the default emails text in UTF-8 plain text encoding
User=	^	[SMTP]	Release 3.11.0	Internet Settings → Email Server Settings	Username	(blank)	Text box where you enter user name needed to authenticate with your SMTP email server

Charts

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

Charts have evolved rapidly in MX development, this table needs verification by somebody who uses the functionality documented here. Can you be the contributor to bring it up to date?

Parameter Line Entry	File Section	Introduced	MX Section	Label on Settings page	Default	Description
GraphHours=24	[Graphs]	Legacy Cumulus	Station Settings → Graphs	Graph hours	24 (2 rolling days worth of values)	For those plots that show values (if available) minute by minute, how many days back to go. Some people prefer to set this to 48 or 96, that means uploading a lot more data in the .json files, but it shows more on charts
AppTempVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Apparent temperature	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Australian Apparent Temperature plotted on Charts
BaseTemperature1=	[GrowingDD] and [TempSum]	Release 3.11.0 - b3129	Station Settings → Growing Degree Days	Base temperature #1	Depends on selected temperature units (not quite same) (Celsius) 5 (equivalent to 41 ^oFahrenheit) (Fahrenheit) 40 (equivalent to 4.44 ^oCelsius)	Base temperature for series 1
BaseTemperature2=	[GrowingDD] and [TempSum]	Release 3.11.0 - b3129	Station Settings → Growing Degree Days	Base temperature #1	Depends on selected temperature units (equivalent) (Celsius) 10 (Fahrenheit) 50	Base temperature for series 2
Cap30C=1	[GrowingDD]	Release3.11.0 - b3129	Station Settings → Growing Degree Days	Cap GDD at 30°C / 86°F	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want growing degree days capped and not incremented at high temperatures (threshold shown in setting name)
ChartMaxDays=31	[Graphs]	Legacy Cumulus	Station Settings → Graphs	Graph Days	31 (daily values)	For those plots that show recent daily values, this states how many of them to plot
Colour0=#058DC7, Colour1=#50B432, Colour2=#ED561B, Colour3=#DDDF00, Colour4=#24CBE5, and Colour5=#64E572	[Select-a-Chart]	Release 3.9.7 - b3107	???	???	Hex colours as shown in parameter list	Colour of line used for plotting the respective series
DailyAvgTempVisible=1	[Graphs]	Release 3.11.0 - b3129	Station Settings → Graphs → Visibility → Temperature Data	Daily Average Temperature	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Daily (integrated) Average temperature plotted on Charts
DailyMaxTempVisible=1	[Graphs]	Release 3.11.0 - b3129	Station Settings → Graphs → Visibility → Temperature Data	Daily Maximum Temperature	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Daily Maximum temperature plotted on Charts
DailyMinTempVisible=1	[Graphs]	Release 3.11.0 - b3129	Station Settings → Graphs → Visibility → Temperature Data	Daily Minimum Temperature	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Daily Minimum temperature plotted on Charts
DPVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Dew Point plotted on Charts
FeelsLikeVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Feels Like Temperature plotted on Charts
GrowingDegreeDaysVisible1=1	[Graphs]	Release3.11.0 - b3129	Station Settings → Graphs → Visibility → Degree Days	Growing Degree Days series #1	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see series 1 plotted on Charts
GrowingDegreeDaysVisible2=1	[Graphs]	Release3.11.0 - b3129	Station Settings → Graphs → Visibility → Degree Days	Growing Degree Days series #2	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see series 2 plotted on Charts
HIVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see USA Heat Index plotted on Charts
HumidexVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Canadian Humidity Index plotted on Charts
InHumVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Humidity Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Indoor Relative Humidity plotted on Charts
InTempVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Indoor Temperature plotted on Charts
OutHumVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Humidity Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Outdoor Relative Humidity plotted on Charts
Series0= to Series5=	[Select-a-Chart]	Release 3.9.7 - b3107	???	???	0 (disabled)	Name of parameter to plot (in series 0 to 5) e.g. "Pressure", "Wind Gust", "Temperature", "Rainfall Rate", "Wind Bearing"
SolarVisible=1	[Graphs]	MX release 3.10.0	Station Settings → Graphs → Visibility → Solar Data	UV Index	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Solar radiation plotted on Charts
SunshineVisible=1	[Graphs]	MX release 3.10.0	Station Settings → Graphs → Visibility → Solar Data	UV Index	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Sunshine Hours plotted on Charts
TempSumVisible0=1	[TempSum]	Release 3.11.0 - b3129	Station Settings → Annual Temperature Sum	Annual Temperature Sum 0	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Annual Temperature Sum series 0 plotted on Charts
TempSumVisible1=1	[TempSum]	Release 3.11.0 - b3129	Station Settings → Annual Temperature Sum	Annual Temperature Sum #1	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Annual Temperature Sum minus baseline 1 plotted on Charts
TempSumVisible2=1	[TempSum]	Release 3.11.0 - b3129	Station Settings → Annual Temperature Sum	Annual Temperature Sum #2	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Annual Temperature Sum minus baseline 2 plotted on Charts
TempSumYearStart=	[TempSum]	Release 3.11.0 - b3129	Station Settings → Annual Temperature Sum	Year summation starting month	Depends on hemisphere (Northern hemisphere) 1 = January (Southern hemisphere) 7 = July	Enter as a number the month for which (on first of that month) annual temperature summation is reset to zero
TempVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Outdoor Temperature plotted on Charts
UVVisible=1	[Graphs]	MX release 3.10.0	Station Settings → Graphs → Visibility → Solar Data	UV Index	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Ultra Violet Index plotted on Charts
WCVisible=1	[Graphs]	MX release 3.7.0 - b3089	Station Settings → Graphs → Visibility → Temperature Data	Dew point	Ticked (shown in Cumulus.ini as 1)	Simple tick or not indicating whether you want to see Wind Chill plotted on charts
YearStarts=	[GrowingDD]	Release 3.11.0 - b3129	Station Settings → Growing Degree Days	Growing season starting month	Depends on hemisphere (Northern hemisphere) 1 = January (Southern hemisphere) 7 = July	Enter as a number the month for which (on first of that month) Growing degree days is reset to zero

Data Logging

Available in all Cumulus releases
File Section is [Station]

Parameter Line Entry	Shown on Settings page?	MX Section	Label on Settings page	Default	Description
DataLogInterval=2	(Always)	Station settings → General Settings	Log interval	2 (10 minutes)	Drop-down: 0 = 1 minute between MX logs into the one to three Monthly_log_files (i.e. Standard log files, and optionally Extra Sensor Files, Air_Link_Log.txt) 1 = 5 minutes between MX logging lines 2 = 10 minutes between MX logging lines 3 = 15 minutes between MX logging lines 4 = 20 minutes between MX logging lines 5 = 30 minutes between MX logging lines
LogExtraSensors=0	(Depends on station type) Only from Release 3.12.0	Station settings → Common Options	Extra sensors	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if your weather station can output readings to be logged in Extra Sensor Files Don't tick (value shown as 0 in Cumulus.ini) if you have nothing to log to Extra Sensor Files.
NoSensorCheck=0	(not yet on a settings page)	(not known)	(not known)	0 (normal)	Boolean: 0 = MX will stop if any of the minimum set of sensors listed below fails 1 = MX will continue to run, even if any of the minimum set of sensors listed below fails Minimum set of sensors: Current air temperature Current Relative Humidity At least one wind speed Current air pressure (absolute or sea-level) Cumulus will stop processing any information from a weather station unless the above 4 source values are being supplied and reveal they are being updated (failure is set is after a total of 6 unsuccessful consecutive attempts to read each of these).
RainDayThreshold=-1	(with warning: "Here be dragons!")	Depends on release: (3.5.1 to 3.11.4) Manual edit of file (3.12.0 onwards) Station settings → Common Options → Advanced options	Rain day threshold	-1 (that represents 0.2 mm or 0.01 inches)	The amount of rainfall that must be collected before MX treats today as a wet day The intention is this will represent more than one tip, as the first tip might contain some rain from an earlier day
RolloverHour=0	(Always)	Station settings → Log Rollover	Time	0 (midnight)	Radio type selection: 0 = MX will do an end of day process when the time (on Weather Station if it provides time) reaches midnight 1 = MX will do an end of day process when the time (on Weather Station if it provides time) reaches 9 a.m. local standard/winter time
SnowDepthHour=0	(with warning: "Here be dragons!")	Depends on release: (3.5.1 to 3.11.4) Manual edit of file (3.12.0 onwards) Station settings → Common Options → Advanced options	Snow depth hour	0 (midnight)	Spin selector of 0 to 23: Defines hour from which entries in Weather Diary for current calendar day are used. Prior to this hour the weather diary will be searched for Calendar yesterday
StartDate=	(with warning: "Here be dragons!")	Station Settings → Common Options → Advanced Options	Records Began date	(Set when you first use Cumulus)	Format used is determined by locale used for running MX. If this date is edited, keep to same format. MX generally (see Calculate_Missing_Values#CreateMissing.exe for exceptions) ignores any data file entries prior to this date.
UseDataLogger=1	(probably determined by station type)	(not known)	(not known)	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if your weather station has its own storage, so MX can do a catch up when it first starts and read any "archive data" Don't tick (value shown as 0 in Cumulus.ini) if your weather station has no storage, and therefore MX cannot capture any readings when it is not running
Use10amInSummer=1	(Always)	Station settings → Log Rollover	Use 10am in Summer	1 (normal)	Tick box: 0 = If "Daylight Saving Time" (DST) applies in Summer, If rollover time is midnight, then rolls over at midnight local time, regardless of whether DST is in operation or not If rollover time is 9 a.m., MX is to use 9 am local time, regardless of whether DST is in operation or not 1 = Normal behaviour: If rollover time is midnight, then rolls over at midnight local time, regardless of whether DST is in operation or not If MX would do an end of day process when the time (on Weather Station if it provides time) reaches 9 a.m. local standard/winter time, then it waits until 10 a.m. local time while DST is in effect

Debugging

Available from beta MX.
File Section is [Station]

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
Logging=1	Depends on release installed: Alternatives: (Releases 3.0.0 to 3.9.8) Close Cumulus MX, then edit Cumulus.ini configuration file, and add a line in the [Station] section: Logging = 1, then restart Cumulus MX. (Releases 3.1.0 to 3.9.3) Station Settings &rarr Options (Release 3.9.4 to 3.11.4) Program Settings → Program General Options (Release 3.12.0 onwards) Program Settings → Logging Options	Debug logging	0 (disabled)	This adds extra information about data transfers between your weather station and MX. It was introduced originally for Davis stations only, but later (can someone insert here the relevant release) extended to cover more stations.
DataLogging=1	Depends on release installed: Alternatives: (Releases 3.0.0 to 3.9.8) Close Cumulus MX, then edit Cumulus.ini configuration file, and add a line in the [Station] section: DataLogging = 1, then restart Cumulus MX. (Releases 3.1.0 to 3.9.3) Station Settings &rarr Options (Release 3.9.4 to 3.11.4) Program Settings → Program General Options (Release 3.12.0 onwards) Program Settings → Logging Options	Debug logging	0 (disabled)	This adds extra information about both data transfers initiated from MX, and all the internal MX processes.

Display Options

File Section is [Display]
MX Section is Station Settings → Display Options

Parameter Line Entry	Introduced	Label on Settings page	Default	Description
DisplaySolarData=0	??? 3.10.0 ???	Display Solar data	Unticked (shown as 0 in Cumulus.ini)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to display solar data in tables shown on the web pages provided in webfiles folder (from release 3.10.0 onwards) Don't tick (value shown as 0 in Cumulus.ini) if you want MX to suppress the table cells that would display solar data
DisplayUvData=0	??? 3.10.0 ???	Display UV-I data	Unticked (shown as 0 in Cumulus.ini)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to display ultra-violet intensity data in tables shown on the web pages provided in webfiles folder (from release 3.10.0 onwards) Don't tick (value shown as 0 in Cumulus.ini) if you want MX to suppress the table cells that would display UV intensity data
NumWindRosePoints=16	Legacy Cumulus	Number of wind rose points	16	Drop-down determining if weather station bearing supplied by weather station is to be converted to 8 or 16 compass directions (i.e. whether to include or exclude (in English) NNE, ENE, ESE, SSE, SSW, WSW, WNW, and NNW 8 points 16 points Despite what it says in the hint on the settings page, leave at default whichever weather station type you use, unless this actually causes you a problem. The parameter was introduced by Steve Loft. Davis wind vanes use a potentiometer to measure wind direction so send Cumulus a bearing that can vary continuously between 1 and 360 degrees. Fine Offset wind vanes use magnetic switches that depend on the magnet under the moving part selecting two switches in the fixed part for the vane being exactly in-between compass directions, and selecting one switch for the main 8 directions and slightly away from the main directions; so they have a bias against sending Cumulus the in-between directions.
UseApparent=1	??? MX 3.6.0 or 3.10.0 ???	Use Apparent Temperature	Ticked (shown as 1 in Cumulus.ini)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to display apparent temperature in tables shown on the web pages provided in webfiles folder (from release 3.10.0 onwards) for consistency with Cumulus prior to release 3.6.0 Don't tick (value shown as 0 in Cumulus.ini) if you want MX to display feels like temperature in tables shown on the web pages provided in webfiles folder (from release 3.10.0 onwards) for consistency with Cumulus from release 3.6.0

Extra Web Files

There are 100 occurrences of each parameter in Cumulus.ini, and therefore each parameter has a base name followed by numbers 0 to 99.

The settings interface presents the rows on multiple pages, the rows are not numbered, so you have to do some counting to work out which row in the admin interface page corresponds with which parameter in Cumulus.ini file.

You MUST restart MX after any changes in this section, before the new settings take effect.

Parameter Line Entry	Label on Settings page	Default	Description
[FTP site]			Section name
ExtraLocal0= to ExtraLocal99=	Local File Name	(empty)	You can enter: A relative path name, with respect to the "CumulusMX" root folder e.g. ./data/dayfile.txt (Note: this is the daily summary log file, see link for how it can be used on a web server) e.g. ./webMX/betel_monthlyrecord_liteMXT.html (Note: this is a third party template file - see Alternative Monthly Extremes using <#webtag>s e.g. ./web/trendsT.htm (Note: That file is not part of default web site any more, but serves as another example A full path name for a file on the computer running MX e.g. /home/pi/documents/myFile e.g. C:\Users\Public\Documents\working.txt You can place any of the following special tags into the entry These should be typed as shown on their own <noaayearfile> and <noaamonthfile> these respectively represent latest yearly and latest monthly reports <currentlogfile>, <currentextralogfile>, and <airlinklogfile> these respectively represent standard, extra sensor, and Davis AirLink air quality monitor log files e.g. ExtraLocal3=<currentlogfile>
ExtraRemote0= to ExtraRemote99=	Destination Filename	(empty)	Defines where MX is to upload file to If file transfer is requested (see below), the file path should be expressed starting at the FTP/FTPS/SFTP root I can't tell you what the file path is for your web server, but I can give a couple of examples to steer you e.g. httpdocs/dayfile.txt e.g. public_html/thismonthyear.htm If the FTP is not ticked, the file path should be full path for a file on the computer running MX e.g. /var/www/html/weather/images/moon.png could be destinatation for uploading the MX generated moon image to a Linux hosted server e.g. /var/www/html/weather/webfilesMX/tempdata.json for uploading one of the files with graph data to a Linux hosted server You can place any of the following special tags into the entry These should be typed as shown as part of the destination path, note that they can be used: either to represent the final filename part of the path e.g. ExtraRemote3=/var/www/html/weather/monthly/<currentlogfile> or to modify a filename, so it becomes unique to a particular month e.g. ExtraRemote0=/var/www/html/weather/cumulus_generated/savedFiles/web_tags_real_time_<currentlogfile>.inc <noaayearfile> and <noaamonthfile> these respectively represent latest yearly and latest monthly reports <currentlogfile>, <currentextralogfile>, and <airlinklogfile> these respectively represent standard, extra sensor, and Davis AirLink air quality monitor log files
ExtraProcess0= to ExtraProcess99=	Process	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if the local file is a template file, see here for full explanation of Process Don't tick (value shown as 0 in Cumulus.ini) if you want local file uploaded with existing content
ExtraRealtime0= to ExtraRealtime99=	Realtime	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if See #Realtime Settings, you must have "Enable realtime" ticked, and defined an interval there Uploads the file to destination specified at interval defined Don't tick (value shown as 0 in Cumulus.ini) if you want uploading to happen at a different interval (e.g. Standard interval)
ExtraFTP0= to ExtraFTP99=	FTP	1	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to use the FTP protocol specified in #Web/FTP Site Don't tick (value shown as 0 in Cumulus.ini) if the remote file is on the computer running MX and a simple Copy File is required
ExtraUTF0= to ExtraUTF99=	UTF-8	1	Please see technical guidance on encoding Tick (value shown as 1 in Cumulus.ini) for default, modern files use UTF-8 encoding, this can display an extended range of characters If unticked (0 appears in file), then iso-8859-1 encoding is used
ExtraBinary0= to ExtraBinary99=	Binary	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if your file is e.g. an image file (e.g. moon.png) Don't tick (value shown as 0 in Cumulus.ini) if the file is text, HTML, PHP script, JSON, JavaScript
ExtraEOD0= to ExtraEOD99=	End of Day	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if your file is to be uploaded during the End of Day process Don't tick (value shown as 0 in Cumulus.ini) if you want uploading to happen at a different interval (e.g. Standard interval)

Location

Introduced for legacy Cumulus
File Section is [Station]

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
Altitude=0	Station Settings → Location	Altitude	0	The height above mean sea level where the (pressure) sensor is positioned
AltitudeInFeet=1	Station Settings → Location	Altitude Units	Default depends on release: Legacy until 3.11.4: 1 (labelled as feet) From 3.12.0: 0 (labelled metres)	Radio Setting feet (value shown as 1 in Cumulus.ini) metres (value shown as 0 in Cumulus.ini)
LocName=	Station Settings → Location	Name	(empty)	A short name for the location
LocDesc=	Station Settings → Location	Description	(empty)	A longer description for the location
"Latitude=0" and "LatTxt="	Station Settings → Location → Latitude	"Degrees", "Minutes", "Seconds", and "Hemisphere → North or South"	(blank)	The selections made on this Settings Page sub-section will place the appropriate content in the two parameters in the file
"Longitude=0" and "LongTxt="	Station Settings → Location → Longitude	"Degrees", "Minutes", "Seconds", and "Hemisphere → East or West"	(blank)	The selections made on this Settings Page sub-section will place the appropriate content in the two parameters in the file

Optional Structured Query Language Settings

SQL is structured in the sense that keywords have to appear in the correct order, and there are rules about which words are mandatory. SQL is not just for running queries that read database tables, it can create database tables, give and revoke permissions, and do many more maintenance type tasks. SQL is a language in that each variant of SQL has a vocabulary and set of rules that are specific to that database server, although there is a sub-set, that is set by "ANSI", of words and constructions that all SQL dialects should obey.

MX uses two types of SQL. One type is for SQLite database (see Cumulusmx.db and Diary.db, that type stores data in rows that are numbered, and columns that are named. In a retrieval query you can sort ascending/descending on value in any column. You can select a row by specifyimg content, but that gets translated into a row number to actually determine what is updated.

The file section [MySQL] is about a different type of database (i.e. Maria database, or Oracle MySQL) these implement a relational database that has to satisfy the rule that all data appears in a table with rows and columns. The columns have a particular order, but there is no control over the order of rows, so you can't specify a row number, you either specify a primary key that identifies a particular row, or you specify that what is returned from query should be sorted in an ascending/descending order of the value in a specified column.

Both "CumulusMX.exe" and "ExportToMySQL.exe" make use of the following settings:

Executable	Function	Description
CumulusMX.exe	Data Logs menu	An option "Update MySQL on Edit" allows you to decide whether MX issues SQL when you edit a data log or "dayfile.txt", so the same edit is made to the corresponding database table, provided that the table has been created with the default name and has the column names defined by default.
CumulusMX.exe	Settings menu → MySQL settings → General Options	An option "Buffer commands on failure" allows you to decide whether MX tries to run SQL commands again, if they fail. IMPORTANT: This is to cope with failure due to the database server going down; the option should not be ticked if you are testing new "custom" SQL and may have made a mistake in the coding. You need to ensure the SQL is either generated by MX as a fixed query, or has been tested and is correct synta before considering this option.
	Settings menu → MySQL settings → Realtime.txt Upload	An option that can be enabled that automatically updates a "Realtime" table, each new row is effectively what is stored in the file realtime.txt.
	Settings menu → MySQL settings → Dayfile.txt Upload	An option that can be enabled that at end of day ensures that a new line is added to dayfile.txt and a new row (with similar data) is inserted into a "Dayfile" table.
	Settings menu → MySQL settings → Monthly log file Upload	An option that can be enabled that automatically updates a "Monthly" table, every time a new line is added to the standard data log file.
	Settings menu → MySQL settings → Custom Upload - seconds interval	An option that can be enabled that runs some predetermined SQL every time the specified number of seconds has elapsed.
	Settings menu → MySQL settings → Custom Upload - minutes interval	An option that can be enabled that runs some predetermined SQL every time the specified number of minutes has elapsed.
	Settings menu → MySQL settings → Custom Upload - at rollover	An option that can be enabled that runs some predetermined SQL just after dayfile.txt has had a new line, but before other end-of-day actions occur.
ExportToMySQL.exe	parameters to utility	Determine which file read (and therefore which table updated, using table names set in table name parameters explained in next table)

WARNING: The SQL syntax for "My SQL Connector" used by .NET and therefore by MX, differs in various ways from the MySQL Client or MARIA db syntax.

Here is an example of what might be input as "predetermined SQL", showing how you can use conditionals and web tags:

INSERT IGNORE INTO table_name_1 (primary_key, column_name_1, column_name_2 ....) VALUES ('<#primary_key>', '<#web tag_name_1 modifier_1>', '<#web tag_name_2 modifier_2>'   ....);


BEGIN NOT ATOMIC
IF '<#web tag>' = '---' THEN 
simpler query to run if something not numeric;
ELSE 
UPDATE table_name_2 SET  column_name_1 = '<#web tag_name_1 modifier_1>', column_name_2 =  '<#web tag_name_2 modifier_2>'   ....   WHERE primary_key = '<#primary_key>';
END IF
END;

Introduced in Cumulus MX 3.0.0 beta
File Section is [MySQL]
MX page is Settings menu → MySQL settings

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
BufferOnFailure=0	General Options	Buffer commands on failure	0 = ignore errors	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to store any commands that fail (see note above), and try them again (stored commands lost if MX is stopped) Don't tick (value shown as 0 in Cumulus.ini) if you want MX to ignore any errors
CustomMySqlMinutesCommandString=	Custom Upload - minutes interval	"SQL command" only shown if next parameter is ticked	(empty)	See "predetermined SQL" example above
CustomMySqlMinutesEnabled=0	Custom Upload - minutes interval	Custom Minutes Enabled	0 = don't display other options	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want the previous and next options to be displayed, and actioned Don't tick (value shown as 0 in Cumulus.ini) if MX is not to action the previous and next settings
CustomMySqlMinutesIntervalIndex=6	Custom Upload - minutes interval	Interval:	6 = 10 minutes	Drop-down list of predetermined intervals: 0 = 1 minute 1 = 2 minutes 2 = 3 minutes 3 = 4 minutes 4 = 5 minutes 5 = 6 minutes 6 = 10 minutes 7 = 12 minutes 8 = 20 minutes 9 = 30 minutes 10 = 1 hour (60 minutes)
CustomMySqlRolloverCommandString=	Custom Upload - at rollover	"SQL command" only shown if next parameter is ticked	(empty)	See "predetermined SQL" example above
CustomMySqlRolloverEnabled=0	Custom Upload - at rollover	Custom Rollover Enabled	0 = don't display other options	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want the previous and next options to be displayed, and actioned Don't tick (value shown as 0 in Cumulus.ini) if MX is not to action the previous and next settings
CustomMySqlSecondsCommandString=	Custom Upload - seconds interval	"SQL command" only shown if next parameter is ticked	(empty)	See "predetermined SQL" example above
CustomMySqlSecondsEnabled=0	Custom Upload - seconds interval	Custom Seconds Enabled	0 = don't display other options	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want the previous and next options to be displayed, and actioned Don't tick (value shown as 0 in Cumulus.ini) if MX is not to action the previous and next settings
CustomMySqlSecondsInterval=10	Custom Upload - seconds interval	Interval (seconds):	10	A number field, takes 1 to 59
Database=	Server details	Database name:	(empty)	A text field where you enter the name of the database your tables are to be created/updated in
DayfileMySqlEnabled=0	Dayfile.txt upload	Dayfile Enabled	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to at end of day ensure that a new line is added to dayfile.txt and a new row (with similar data) is inserted into a "Dayfile" table Don't tick (value shown as 0 in Cumulus.ini) if MX is only to ensure that a new line is added to dayfile.txt
DayfileTable=	Dayfile.txt upload	Table name	Dayfile	Having defined this table, and saved the settings, click the "Create Dayfile" button to create the database table with the standard column names. If you change the name here, normal updates and "ExportToMySQl.exe" will use the table name you define, but the option to update table when you edit "dayfile.txt" will fail (and if set to do so, keep failing as it repeats).
Host=Localhost	Server details	Host name	(empty)	Set to whatever host name your database server has specified, if you host Your_Own_Server, then you may be able to use "Localhost".
MonthlyMySqlEnabled=0	Monthly logfile upload	Monthly Log Enabled	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to at your standard logging interval ensure that a new line is added to standard data log file and a new row (with similar data) is inserted into a "Monthly" table. Don't tick (value shown as 0 in Cumulus.ini) if MX is only to ensure that a new line is added to standard data log file
MonthlyTable=	Monthly logfile upload	Table name	Monthly	Having defined this table, and saved the settings, click the "Create Monthly" button to create the database table with the standard column names. You might wish to change the name here once a year, to stop the database table getting enormous, if so you might name the table something like "standard2020". If you change the name here, normal updates and "ExportToMySQl.exe" will use the table name you define, but the option to update table when you edit "MMMyyyyLog.txt" will fail (and if set to do so, keep failing as it repeats).
Pass=	Server details	Password	(empty)	Set to whatever password is used for update access with the database user name (see below)
Port=3306	Server details	Port number	3306	The port related to the host name (defined above) for update access to your database server
RealtimeMySql1MinLimit=0	Realtime.txt upload	Limit Inserts:	0 = false	Simple tick or not Tick (value shown as 1 in Cumulus.ini) Don't tick (value shown as 0 in Cumulus.ini) See explanation beside and below setting
RealtimeMySqlEnabled=0	Realtime.txt upload	Real time Enabled	0 = don't display other options	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to at your real time interval ensure that a new realtime.txt file is created and a new row (with similar data) is inserted into a "Realtime" table. Don't tick (value shown as 0 in Cumulus.ini) if MX is only to ensure that a new line is added to standard data log file
RealtimeRetention=	Realtime.txt upload	Data Retention value and Data Retention unit	"7" and "Days"	The value field will take any number, the unit field is a dropdown: Seconds Minutes Hours Days Weeks Months Taken together, these determine the period for which rows are kept in the table named in "RealtimeTable", any row older than this specification will be deleted as part of the automatic SQL
RealtimeTable=Realtime	Realtime.txt upload	Table name	Realtime	Having defined this table, and saved the settings, click the "Create Realtime" button to create the database table with the standard column names. Remember that you can tailor the contents of "realtime.txt", if you want non-standard columns in this table, you have to create the table yourself.
UpdateOnEdit=1	General Options	Update MySQL on Edit	1 = update the table when edit the file	Simple tick or not Tick (value shown as 1 in Cumulus.ini) Don't tick (value shown as 0 in Cumulus.ini) Please see begining of previous table for explanation and warning about how all defaults must be set for this to work
User=	Server details	User name	(empty)	Database access user name, that matches with password described earlier

Optional Report Settings

File Section is [NOAA]

Parameter Line Entry	Introduced	MX Section	Label on Settings page	Default	Description
AutoCopy=0	Release 3.12.0	NOAA Reports Settings → FTP Options	Auto Copy NOAA report files	0 (disable)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if your report is to be copied to copy directory during the End of Day process Don't tick (value shown as 0 in Cumulus.ini) for no copy action
AutoFTP=0	First with Cumulus 2	NOAA Reports Settings → FTP Options	Auto transfer NOAA report files	0 (disable)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) to enable the file transfer process you have defined for MX, to upload the file for you (at first update time after rollover has completed) Don't tick (value shown as 0 in Cumulus.ini) to disable any file transfer process
AutoSave=1	First with Cumulus 2	NOAA Reports Settings	Create NOAA files after daily rollover	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want MX to use the (optional) Reports functionality Don't tick (value shown as 0 in Cumulus.ini) if MX Reports functionality not required
City=	First with Cumulus 2	NOAA Reports Settings → Site Details	City	(empty)	Enter here your hamlet, village, town, or city, name
CoolingThreshold=22	First with Cumulus 2	NOAA Reports Settings → Thresholds	Cooling threshold	65^o F or 18.3^oC	Cold Degree Days are a measure of the need to cool the air to make it more comfortable, based on time above, and temperature difference above, a threshold temperature. An international standard says 22 ^oCelsius is a suitable threshold to ensure comfort. For historical consistency, the default used by MX is based on the threshold used when Steve Loft first implemented this in Cumulus 2 (enhancement request 44), and that was done to match some early look up tables.
CopyDirectory=	Release 3.12.0	NOAA Reports Settings → Report Options	Copy Directory	(empty)	The folder on the web server you host to which reports are to be copied
FTPDirectory=	First with Cumulus 2	NOAA Reports Settings → FTP Options	destination folder	Depends on release: (3.1.0 to 3.11.4) blank (3.12.0 onwards) to match change in default web site script specification of Reports folder	Specify the destination folder for file transfer to, on your FTP server Leave at default (for your release) and MX will work with the default web pages script supplied (at same release) Specify a folder relative to FTP root, and MX will upload reports to that folder instead (you are then responsible for writing any script on your web site to find each report and do any processing).
HeatingThreshold=15.5	First with Cumulus 2	NOAA Reports Settings → Thresholds	Heating threshold	65^o F or 18.3^oC	Heating Degree Days are a measure of the need for heating, based on time below, and temperature difference below, a threshold temperature. An international standard says 15.5 ^oCelsius is a suitable threshold to ensure comfort. For historical consistency, the default used by MX is based on the threshold used when Steve Loft first implemented this in Cumulus 2 (enhancement request 44), and that was done to match some early look up tables.
MaxTempComp1=22	First with Cumulus 2	NOAA Reports Settings → Thresholds	Max temp comparison 1	(empty)	The report will count the number of days when this threshold is exceeded. In the parameter I have quoted, the first comparison has been set to agree with the cooling degree day threshold in Celsius. Express in Fahrenheit if that is your chosen unit
MaxTempComp2=0	First with Cumulus 2	NOAA Reports Settings → Thresholds	Max temp comparison 2	(empty)	The report will count the number of days when this threshold is exceeded. In the parameter I have quoted, the second comparison has been set to agree with feezing point (I’m using Celsius). Express in Fahrenheit if that is your chosen unit
MinTempComp1=15.5	First with Cumulus 2	NOAA Reports Settings → Thresholds	Min temp comparison 1	(empty)	The report will count the number of days when this threshold is exceeded. In the parameter I have quoted, the first comparison has been set to agree with the heating degree day threshold in Celsius. Express in Fahrenheit if that is your chosen unit
MinTempComp2=0	First with Cumulus 2	NOAA Reports Settings → Thresholds	Min temp comparison 2	(empty)	The report will count the number of days when this threshold is exceeded. In the parameter I have quoted, the second comparison has been set to agree with feezing point (I’m using Celsius). Express in Fahrenheit if that is your chosen unit
MonthFileFormat='NOAAMO'MMyy'.txt'	First with Cumulus 2	NOAA Reports Settings → Output Files	Monthly filename format	'NOAAMO'MMyy'.txt' (note quotes round NOAAMO and round .txt)	Here you specify the filename template for MX to use when reading, or writing, monthly reports There is a prefix text in quotes,then comes a way to specify months (see Reports_folder#NOAA_style_Report_Naming), and finally comes the mandatory text extension. e.g. "NOAAMO"MMMyyyy".txt" would also be valid.
Name=Personal Weather Station	First with Cumulus 2	NOAA Reports Settings → Site Details	Site Name	(empty)	What you would like to see in report title for your station name
NOAAUseUTF8=1	First with Cumulus 2	NOAA Reports Settings → Report Options	Use UTF-8 encoding	1 (UTF-8)	Please see Reports_folder#Encoding Tick (value shown as 1 in Cumulus.ini) for default, modern files use UTF-8 encoding, this can display an extended range of characters, including the ^o degree symbol If unticked (0 appears in file), then iso-8859-1 encoding is used, this has a more restricted range of characters, and the ^o degree symbol is coded differently
RainComp1=0.5	First with Cumulus 2	NOAA Reports Settings → Thresholds	Rain comparison 1	(empty)	The report will count the number of days when the daily rainfall exceeds this threshold. In the parameter I have quoted, the first comparison has been set to the same as I have set else where as my significant rain threshold
RainComp2=	First with Cumulus 2	NOAA Reports Settings → Thresholds	Rain comparison 2	(empty)	The report will count the number of days when the daily rainfall exceeds this threshold.
RainComp3=	First with Cumulus 2	NOAA Reports Settings → Thresholds	Rain comparison 3	(empty)	The report will count the number of days when the daily rainfall exceeds this threshold.
State=	First with Cumulus 2	NOAA Reports Settings → Site Details	State	(empty)	Enter here your local authority area or region (state in USA)
UseDotDecimal=0	Release 3.9.5 - b3100	NOAA Reports Settings → Report Options	Use a 'dot' decimal point	0 (disable)	Formatting real numbers for when NOAA report parsed by a script Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want NOAA reports to use decimal point even if locale says use decimal comma Don't tick (value shown as 0 in Cumulus.ini) if NOAA reports use the integer/decimal separator specified by locale
UseMinMaxAvg=0	Release 3.12.0	NOAA Reports Settings → Report Options	Use WHO average or Integrated average	0 (integrated average)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) if you want temperature averages quoted in NOAA reports to use WHO approach: (min + max)/2 Don't tick (value shown as 0 in Cumulus.ini) if you want temperature averages quoted in NOAA reports to use integrated calculation: Sum of all temperature measurements divided by count of measurements
YearFileFormat='NOAAYR'yyyy'.txt’	First with Cumulus 2	NOAA Reports Settings → Output Files	Yearly filename format	'NOAAYR'yyyy'.txt'	Here you specify the filename template for MX to use when reading, or writing, yearly reports There is a prefix text in quotes,then comes a way to specify months (see Reports_folder#NOAA_style_Report_Naming), and finally comes the mandatory text extension.
12hourformat=0	???	NOAA Reports Settings → Output Files	Time format	0 (24 hour)	How times are output on reports 24 Hour (value shown as 0 in Cumulus.ini) 12 Hour (value shown as 1 in Cumulus.ini)

Normal Mean Temperatures

File Section is [NOAA]
The parameters run from ‘’’NOAATempNormJan=’’’ to ‘’’NOAATempNormDec=’’
There is one box labelled for each month on the settings screens
All the defaults are (blank)
What you enter is the mean temperature, long-term averages (say over 10 or 30 years if available) say is expected that month, often taken from local climate statistics, or your own past measurements

Normal Precipitation

File Section is [NOAA]

Rainfall equivalents of mean temperature described above

Optional Third-party Upload Settings

Parameter Line Entry	File Section	MX Section	Action on Settings page	Default
ID= pass=-1 server=cwop.aprs.net port=14580 Enabled=0 Interval=9 SendSR=0 APRSHumidityCutoff=0	[APRS]	APRS/CWOP	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
User= Password= Language=en Enabled=0 Interval=900 SendUV=0 SendSR=0 SendSoilTemp=0 SendIndoor=0 SendSoilMoisture=0 SendLeafWetness=0 SendAirQuality=0	[Awekas]	AWEKAS	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
Enabled=0 CatchUp=1 APIkey= StationId= Interval=15	[OpenWeatherMap]	OpenWeatherMap	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
ID= Password= Enabled=0 Interval=15 SendUV=0 SendSR=0 CatchUp=1	[PWSweather]	PWS Weather	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
User= Password= Enabled=0 Interval=60 OauthToken=unknown OauthTokenSecret=unknown TwitterSendLocation=1	[Twitter]	Twitter	Please note that twitter is deprecated, no new settings possible, existing settings can be used by people who migrated from Cumulus 1 with working tokens	Defaults are as shown in list of parameters
Wid= Key= Enabled=0 Interval=10 SendUV=0 SendSR=0 SendAQI=0 SendSoilMoisture=0 SoilMoistureSensor=0 SendLeafWetness=0 LeafWetnessSensor=0	[WeatherCloud]	WeatherCloud	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
Enabled=0 StationUID= Password= Interval=1 SendRain=0	[WindGuru]	Windguru	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
APIkey= StationIdx=0 Enabled=0 Interval=15 SendUV=0 CatchUp=1	[Windy]	Windy.com	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters
ID= Password= Enabled=0 Interval=15 SendUV=0 SendSR=0 CatchUp=1	[WOW]	Met Office WOW	Tick "Enabled" to see list of parameters so you can edit them	Defaults are as shown in list of parameters

Optional Web Server

The settings listed here changed dramatically at both 3.10.0 and 3.12.0 releases, but they have gradually evolved throughout the development of MX.

FRom 3.12.0, MX can optionally either copy files to a web server you host or file transfer files to a commercial web server.

To implement (and customise) this web server functionality, there are many settings as listed alphabetically in this table. The Internet settings page simplifies making settings by providing selections that amend multiple settings in a bulk operation:

Some settings (marked ^ in table) are only displayed if you select I want to use the supplied default web site.
- For these settings, the "Generate" option is enabled in nearly all (see any qualifier) settings
- If you select "Enable file copy of standard files" (default is disabled) then those settings have their "Copy" option enabled in nearly all (see any qualifier) cases, and their "FTP Transfer" option deselected (instead of defaults shown in table)
- If you deselect "Enable file transfer of standard files" (default is enabled) then those settings have their "Copy" option disabled, and their "FTP Transfer" option enabled in nearly all (see any qualifier) cases (as per defaults shown in table)
The default selections assume you have air quality, and solar, sensors; so you may need to disable some of the defaults the above selections have made
If you don't select I want to use the supplied default web site, then all the settings marked ^ are disabled
- This is what you want if you do not use the MX optional web server functionality
- If you have a customised web site, you may want to select I want to use the supplied default web site to see the settings that would otherwise all be disabled, and then pick any options that would be useful to you.

Parameter Line Entry	File Section	Introduced	Shown on Settings page?	MX Section	Label on Settings page	Default	Description
ActiveFTP=0	[FTP site]	Legacy Cumulus	No	Change directly in file as at release 3.11.x	(n/a )	(n/a)	*0 = Disabled (default) 1 = Enabled, Cumulus will use 'active' FTP mode instead of the default 'passive' mode. You should only select active mode if you are having problems with FTP uploads.
Copy-airquality=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	airquality.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the airquality.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have an air quality sensor)
Copy-alldailydegdaydata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailydegdaydata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailydegdaydata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alldailyhumdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailyhumdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailyhumdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alldailypressdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailypressdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailypressdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alldailyraindata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailyraindata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailyraindata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alldailysolardata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailysolardata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailysolardata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Copy-alldailytempdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailytempdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailytempdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alldailywinddata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailywinddata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailywinddata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-alltempsumdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	alldailytempsumdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the alldailytempsumdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-availabledata=0	[FTP site]	Release 3.12.0	^ (once only)	Internet Settings → Graph File Settings	availabledata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the availabledata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-dailyrain=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	dailyrain.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the dailyrain.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-dailytemp=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	dailytemp.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the dailytemp.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-graphconfig=0	[FTP site]	Release 3.12.0	^ (once only)	Internet Settings → Graph File Settings	graphconfig.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the graphconfig.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-humdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	humdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the humdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-pressdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	pressdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the pressdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-raindata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	raindata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the raindata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-solardata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	solardata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the solardata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Copy-sunhours=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	sunhours.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the sunhours.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Copy-tempdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	tempdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the tempdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-wdirdata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	wdirdata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the wdirdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-websitedata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Standard File Settings	websitedata.json → Copy	0 (disabled)	Relates to asking MX to process the websitedataT.json file in web folder Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the resulting websitedata.json to your local web server Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-winddata=0	[FTP site]	Release 3.12.0	^	Internet Settings → Graph File Settings	winddata.json → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the winddata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Copy-wxnow=0	[FTP site]	Release 3.12.0	^ (disabled)	Internet Settings → Standard File Settings	wxnow.txt → Copy	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy that file to your local web server Don't tick (value shown as 0 in Cumulus.ini) to disable
CopyMoonImage=0	[FTP site]	Release 3.12.0	^	Internet Settings → Moon Image	Copy Moon image file	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy moon image file to your local web server (need to select "Generate Moon Image" see MoonImageEnabled= too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-airquality=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	airquality.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the airquality.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailydegdaydata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailydegdaydata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailydegdaydata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailyhumdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailyhumdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailyhumdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailypressdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailypressdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailypressdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailyraindata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailyraindata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailyraindata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailysolardata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailysolardata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailysolarydata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Create-alldailytempdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailytempdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailytempdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alldailywinddata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailywinddata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailywinddata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-alltempsumdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailytempsumdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the alldailytempsumdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-availabledata=0	[FTP site]	Release 3.10.0	^ (once only)	Internet Settings → Graph File Settings	availabledata.json → Generate	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the availabledata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-dailyrain=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailyrain.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the dailyrain.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-dailytemp=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailytemp.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the dailytemp.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-graphconfig=0	[FTP site]	Release 3.10.0	^ (once only)	Internet Settings → Graph File Settings	graphconfig.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the graphconfig.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-humdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	humdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the humdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-pressdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	pressdat.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the pressdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-raindata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	raindata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the raindata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-solardata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	solardata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the solardata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Create-tempdata=1	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailytemp.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the dailytemp.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-sunhours=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailytemp.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the dailytemp.json file Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Create-tempdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	tempdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the tempdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-wdirdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	wdirdata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the wdirdata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-websitedata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	websitedata.json → Generate	1 (enabled)	Relates to asking MX to process the websitedataT.json file in web folder Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to process the websitedataT.json file into websitedata.json Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-winddata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	winddata.json → Generate	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the winddata.json file Don't tick (value shown as 0 in Cumulus.ini) to disable
Create-wxnow=0	[FTP site]	Release 3.10.0	^ (disabled)	(depends on release) (releases 3.10.0 to 3.11.4) Internet Settings → Web/FTP Settings (release 3.12.0 on) Internet Settings → Standard File Settings	wxnow.txt → Generate	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate a wsnow.txt file Don't tick (value shown as 0 in Cumulus.ini) to disable
DeleteBeforeUpload=0	[FTP site]	legacy Cumulus	(always)	(depends on release) (releases 3.0.0 to 3.11.4) Internet Settings → Web Settings → General Settings (release 3.12.0 on) Internet Settings → Web Site → General Settings	Delete before upload	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to issue instruction to delete existing file (with same name) on the web server before it creates the new file Don't tick (value shown as 0 in Cumulus.ini) to disable (this is the option appropriate to most servers)
Directory=	[FTP site]	Legacy Cumulus	(always)	Internet Settings → Web/FTP Site	Remote FTP Directory	(blank)	Directory (including path) on your server to which FTP (if 'Enabled' is enabled) will upload the files. value is left Blank, default, the root position specified by ftp server A path from the starting point as the position specified by ftp server Not used for ExtraRemoteNN parameters
DisableEPSV=0	[FTP site]	Beta Release 3.0.0 build 3045	No	Still Change directly in file as at release 3.11.x	(n/a )	0	*0 = Disabled (default) 1 = Enabled, to use Extended Passive FTP-mode
DisableFtpsExplicit=0	[FTP site]	Release 3.4.0 - Build 3064	No	Change directly in file as at release 3.11.x	(n/a )	0	(change value following attribute) 0 = Disabled (default) use FTPS Explicit mode 1 = Enabled, to use FTPS Implicit mode
Enabled=1	[FTP site]	Release 3.12.0	(always) Controls whether ^ settings have "File Transfer" option enabled	Internet Settings → Interval Configuration	Enable file transfer of standard files	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to enable file transfer of standard files (see rows marked ^ for further selections) Don't tick (value shown as 0 in Cumulus.ini) to disable
EnableLocalCopy=0	[FTP site]	Release 3.12.0	(always) Controls whether ^ settings have "Copy" option enabled	Internet Settings → Interval Configuration	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to enable copying of files (see rows marked ^ for further selections) Don't tick (value shown as 0 in Cumulus.ini) to disable
EnableRealtime=1	[FTP site]	Legacy Cumulus	(always)	Internet Settings → Realtime Settings	Enable Realtime	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate a timer that will permit real time actions Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-airquality=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	airquality.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the airquality.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have an air quality sensor)
Ftp-alldailydegdaydata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailydegdaydata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailydegdaydata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alldailyhumdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailyhumdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailyhumdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alldailypressdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailypressdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailypressdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alldailyraindata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailyraindata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailyraindata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alldailysolardata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailysolardata.json → File Transfer	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailysolardata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Ftp-alldailytempdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailytempdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailytempdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alldailywinddata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alldailywinddata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alldailywinddata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-alltempsumdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	alltempsumdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the alltempsumdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-availabledata=0	[FTP site]	Release 3.10.0	^ (once only)	Internet Settings → Graph File Settings	availabledata.json → File Transfer	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the availabledata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-dailyrain=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailyrain.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the dailyrain.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-dailytemp=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailyrain.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the dailyrain.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-graphconfig=0	[FTP site]	Release 3.10.0	^ (once only)	Internet Settings → Graph File Settings	graphconfig.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the graphconfig.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-humdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	humdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the humdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-pressdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	pressdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the pressdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-raindata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	raindata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the raindata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-solardata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	solardata.json → File Transfer	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the solardata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Ftp-sunhours=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	sunhours.json → File Transfer	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the sunhours.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable (e.g. if you don't have a solar sensor)
Ftp-tempdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	tempdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the tempdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-wdirdata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	wdirdata.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the wdirdata.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-websitedata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Standard File Settings	websitedata.json → File Transfer	0 (disabled)	Relates to asking MX to process the websitedataT.json file in web folder Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the resulting websitedata.json to your local web server Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-winddata=0	[FTP site]	Release 3.10.0	^	Internet Settings → Graph File Settings	dailyrain.json → File Transfer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the dailyrain.json file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
Ftp-wxnow=0	[FTP site]	Release 3.10.0	^ (disabled)	(depends on release) (release 3.10.0 to 3.11.4) Internet Settings → Web/FTP Settings (release 3.12.0 on) Internet Settings → Standard File Settings	wxnow.txt → File Transfer	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer that file to your local web server Don't tick (value shown as 0 in Cumulus.ini) to disable
ForumURL=	[Web Site]	Legacy Cumulus	(always)	(depends on release) (releases 3.0.0 to 3.11.4) Internet Settings → Web Site (release 3.12.0 on) Internet Settings → Miscellaneous	Forum URL	(blank)	Left blank to allow you to choose format 3.10.0 Default web pages use "<a href=\"https://cumulus.hosiene.co.uk/index.php\">forum</a>" Some alternative URL examples: https://cumulus.hosiene.co.uk/index.php (for above example in default web pages) https://cumulus.hosiene.co.uk https://cumulus.hosiene.co.uk/search.php?search_id=active_topics
FTPlogging=0	[FTP site]	Legacy Cumulus	FTP logging	Depends on release installed: (Releases 3.1.0 to 3.10.5) Internet Settings → → Web Settings → General Settings (Releases 3.11.0 to 3.11.4) Program Settings → Program General Options (Release 3.12.0 onwards) Program Settings → Logging Options	(n/a)	(n/a)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX in standard FTP mode add output to ftplog.txt. to issue instruction to the web server so it creates the new file with a new name and then renames it to the required name (this is the option appropriate to most servers) Don't tick (value shown as 0 in Cumulus.ini) to disable updates to ftplog.txt For other types of file transfer (STTP, FTPS), any extra diagnostic information appears in latest log in MXdiags folder
FTPRename=1	[FTP site]	Legacy Cumulus	(always)	(depends on release) (releases 3.0.0 to 3.11.4) Internet Settings → Web Settings → General Settings (release 3.12.0 on) Internet Settings → Web Site → General Settings	FTP rename	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to issue instruction to the web server so it creates the new file with a new name and then renames it to the required name (this is the option appropriate to most servers) Don't tick (value shown as 0 in Cumulus.ini) to disable The chief advantage of using rename is that it minimises the time that the web server cannot serve a file (while it is being updated)
Host=	[FTP site]	Legacy Cumulus	(always)	Internet Settings → Web/FTP Site	Host name	(blank)	This is either the name, or the IP address, of the ftp server to which you connect when you upload pages to your web site.
IncludeMoonImage=1	[FTP site]	Release 3.5.0	(always)	Internet Settings → Moon Image	(FTP) Upload Moon image file	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer moon image file to your local web server (need to select "Generate Moon Image" see MoonImageEnabled= too) Don't tick (value shown as 0 in Cumulus.ini) to disable
IntervalFtpEnabled=1	[FTP site]	Release 3.12.0	??	Internet Settings → Interval Settings	Enable file transfer update interval	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to make standard interval file transfer actions Don't tick (value shown as 0 in Cumulus.ini) if either no web server, or have selected LocalCopyEnabled (see below)
ListWebTags=0	[Station]	Legacy Cumulus	Only from Release 3.12.0	Depends on release: (3.5.1 to 3.11.4) Manual edit of file (3.12.0 onwards) Station settings → Common Options → Advanced options	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to create WebTags.txt file when Cumulus is restarted (contains an unordered list of all the tag names your Cumulus build will recognise and process) Don't tick (value shown as 0 in Cumulus.ini) to disable
LocalCopyEnabled=0	[FTP site]	Release 3.12.0	(always)	Internet Settings → Interval Configuration	Enable local copy update interval	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to make standard interval file copy actions Don't tick (value shown as 0 in Cumulus.ini) if either no web server, or have selected file transfer IntervalFtpEnabled (see previous)
LocalCopyFolder=	[FTP site]	Release 3.12.0	(always)	Internet Settings → Interval Configuration	(blank)	Folder (including path) to which MX will copy the standard files (see rows marked ^ for further selections) if 'EnableLocalCopy' is enabled
MoonImageEnabled=1	[Graphs]	Release 3.5.0	(always)	Internet Settings → Moon Image	Generate Moon Image	^ Default controlled by selection of default web site	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to use System Drawing to modify CumulusMX/web/MoonBaseImage.png and create CumulusMX/web/moon.png Don't tick (value shown as 0 in Cumulus.ini) if you don't need MX to create a "moon.png"
MoonImageSize=	[Graphs]	Release 3.5.0	(always)	Internet Settings → Moon Image	Image size	???	Enter a size (in pixels) for the generated moon image (according to space on your web page)
Password=	[FTP site]	Legacy Cumulus	(always)	Internet Settings → Web/FTP Site	Password	(blank)	The password for your FTP/SFTP/FTPS connection (masked out on settings page, shown in plain text in file)
Port=21	[FTP site]	Legacy Cumulus	(always)	Internet Settings → Web/FTP Site	FTP port	21 (plain FTP)	you normally use either standard FTP (port=21), SSH for FTP i.e. SFTP (port=22), or SSL/TLS (deprecated Secure Sockets Layer and replacement Transport Layer Security) i.e.FTPS (port=990 normally, may be 25). If you get connection refused, messages in the MXdiags log, then you may need to try alternative protocol and/or alternative ports.
RealtimeFTPEnabled=0	[FTP site]	Legacy Cumulus	^	Internet Settings → Realtime Settings	Enable realtime FTP	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to be able to do file transfers at real-time interval Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeGaugesTxtCopy=0	[FTP site]	Release 3.12.0	^	Internet Settings → Realtime Settings	realtimegauges.txt	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the realtimegauges.txt file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeGaugesTxtCreate=0	[FTP site]	Release 3.10.0	^	Internet Settings → Realtime Settings	realtimegauges.txt → Generate	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the realtimegauges.txt file Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeGaugesTxtFTP=0	[FTP site]	Release 3.10.0	^	Internet Settings → Realtime Settings	realtimegauges.txt → File Transfer	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the realtimegauges.txt file Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeInterval=45000	[FTP site]	Legacy Cumulus	^	Internet Settings → Realtime Settings	Realtime interval	45000 milliseconds (45 seconds)	Enter interval time in seconds (decimals allowed), stored in file converted to milliseconds
RealtimeTxtCopy=0	[FTP site]	Release 3.12.0	^	Internet Settings → Realtime Settings	realtime.txt	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to copy the realtime.txt file to your local web server (need to select "Generate" too) Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeTxtCreate=0	[FTP site]	Release 3.10.0	^	Internet Settings → Realtime Settings	realtime.txt → Generate	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to generate the realtime.txt file Don't tick (value shown as 0 in Cumulus.ini) to disable
RealtimeTxtFTP=0	[FTP site]	Release 3.10.0	^	Internet Settings → Realtime Settings	realtime.txt → File Transfer	0	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to file transfer the realtime.txt file Don't tick (value shown as 0 in Cumulus.ini) to disable
RecordSetTimeoutHrs=24	[Station]	Release 3.5.1	Only from Release 3.12.0	Depends on release: (3.5.1 to 3.11.4) Manual edit of file (3.12.0 onwards) Two places: Station setings → General Settings → Advanced options Station settings → Common Options → Advanced options	Depends on where changed (respectively): New record timeout Record set timeout	24	Number of hours before the following web tags are reset: TempRecordSet, WindRecordSet, RainRecordSet, HumidityRecordSet, PressureRecordSet, HighTempRecordSet, LowTempRecordSet, HighAppTempRecordSet, LowAppTempRecordSet, HighHeatIndexRecordSet, LowWindChillRecordSet, HighMinTempRecordSet, LowMaxTempRecordSet, HighDewPointRecordSet, LowDewPointRecordSet, HighWindGustRecordSet, HighWindSpeedRecordSet, HighRainRateRecordSet, HighHourlyRainRecordSet, HighDailyRainRecordSet, HighMonthlyRainRecordSet, HighHumidityRecordSet, HighWindrunRecordSet, LowHumidityRecordSet, HighPressureRecordSet, LowPressureRecordSet, LongestDryPeriodRecordSet, LongestWetPeriodRecordSet, HighTempRangeRecordSet, LowTempRangeRecordSet
Sslftp=	[FTP site]	MX beta	(always)	Internet Settings → Web/FTP Site	Select the FTP Protocol to use	0	Drop down list: 0 = FTP (plain old FTP) - default 1 = Use SSL/TLS (deprecated Secure Sockets Layer and replacement Transport Layer Security) for FTP (FTPS) 2 = Use Secure Shell Home (SSH) for FTP (SFTP)
SshFtpAuthentication=Password	[FTP site]	Release 3.8.2 - build 3092	Only if SFTP selected above	Internet Settings → Web/FTP Site	SFTP Authentication method	Password	Drop down list: 0 = Password 1 = Pre-shared key 2 = Password or pre-shared key
SshFtpPskFile=	[FTP site]	Release 3.8.2 - build 3092	only if 1 or 2 selected in previous setting	Internet Settings → Web/FTP Site	Pre-shared Private Key file for SFTP	(blank)	Filename for your private PSK file, include the full path if the file is not in same folder as CumulusMX.exe
UpdateInterval=60	[FTP site]	legacy software	^	Internet Settings → Interval Settings	Web interval	60	Interval between standard web updates in minutes
Username=	[FTP site]	legacy software	(always)	Internet Settings → Web/FTP Site	Username	(blank)	the user name for connecting to your server
UTF8encode=	[FTP site]	legacy software	(always)	(depends on release) (releases 3.0.0 to 3.11.4) Internet Settings → Web Settings → General Settings (release 3.12.0 on) Internet Settings → Web Site → General Settings	UTF-8 encoding	Default depends on release: (Legacy versions and MX up to 3.9.7) 0 (ISO 8859-1 character set) (Release 3.10.0 on) 1 (UTF-8 encoding enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to use UTF-8 encoding in all .json files Don't tick (value shown as 0 in Cumulus.ini) and MX will create its .json files using ISO 8859-1 character set, please note that this encoding is incompatible with web pages included in webfiles* folder*; so if you upgrade from an earlier release, you may need to change this setting
WebcamURL=	[Web Site]	Legacy Software	(always)	(depends on release) (releases 3.0.0 to 3.11.4) Internet Settings → Web Site (release 3.12.0 on) Internet Settings → Miscellaneous	Webcam URL	(blank)	Can be used to add a link to any other web page, you have on any web server. In default web pages will be labelled as "web cam", but for your own web pages, this might lead to a home or blog page.

Program Start-up Options

Introduced release 3.9.4 - b3099
File Section is [Program]

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
StartupPingHost=	Program Settings → Program Start-up Options	Host to PING on program start-up	None (no remote host)	Add a hostname or IP to address to ping at startup. Cumulus waits until the ping is successful before trying to read from your station. Leave blank to disable
StartupPingEscapeTime=999	Program Settings → Program Start-up Options	PING escape time (mins)	999 (minutes)	Specify a time after which if no ping response is received carry on starting Cumulus MX anyway
StartupDelaySecs=0	Program Settings → Program Start-up Options	Start-up Delay (secs)	zero (no delay)	Add a delay before the Cumulus tries to start reading the station.
StartupDelayMaxUptime=300	Program Settings → Program Start-up Options	Max system uptime to apply the start-up delay	300 (seconds equivalent to 5 minutes)	The time that has passed sice MX was started (up-time) is compared against the (max delay time) figure here. If max delay time less than up-time, the delay specified in previous parameter will NOT be applied If up-time less than this max delay time, then MX will apply any delay specified in previous parameter If this parameter is set to zero, then MX will always apply any delay specified in previous parameter

Proxy

This is a continuation of an experimental legacy Cumulus software feature, please see here for request and see here for potential content. I have not seen any evidence that this feature ever came out of beta, and nobody has ever commented on its use, so I see no reason to do any further documentation.

Station specific alternatives

A number of settings are shown only for specific station types, and so the following tables are grouped here.

Since MX is being developed by someone who uses a Davis station, a lot of "Labels on the Settings Screens" mention "Davis" even if you have selected a different station, because the code was written by copy and paste!

Solar

Cumulus MX is unable to work out if you have a solar sensor, so these options are always displayed.

Parameter Line Entry	File Section	Introduced	MX Section	Label on Settings page	Default	Description
SolarCalc=0	[Solar]	3.13	Station Settings → Solar	Solar Calculation Method	0=Ryan-Stololzenbach	Drop-down list: 0=Ryan-Stololzenbach 1=Bras
SunThreshold=75	[Solar]	3.13	Station Settings → Solar	Sun Threshold (percent)	75	Enter a number
SolarMinimum=0	[Solar]	3.13	Station Settings → Solar	Solar minimum (W/m2)	30	Enter a number
RStransfactorJul=0.80000000000000004	[Solar]	3.14	Station Settings → Solar	RS Transmission factor (June) (Note the internal calculation does apply this to June, but some MX releases were incorrectly typed to say "July" on the settings screen).	0.8	MX does a sinusoidal interpolation between this value and the next. So this June factor changes very little either side of that solstice, with the average value from both factors applying at the equinoxes (March and September) and different amounts of each factor each side of equinox. (So actually more like a cosine interpolation!)
RStransfactorDec=0.80000000000000004	[Solar]	3.14	Station Settings → Solar	RS Transmission factor (December)	0.8	MX does a sinusoidal interpolation between last value and this one. So this December factor changes very little either side of that solstice, with the average value from both factors applying at the equinoxes (March and September) and different amounts of each factor each side of equinox. (So actually more like a cosine interpolation!)
UseBlakeLarsen=0	[Solar]	Legacy	Extra Sensor Settings	Blake-Larsen Sunshine Recorder	0=deselected	checkbox

Selecting the weather station type determines which options are shown

Parameter Line Entry	File Section	Introduced	MX Section	Label on Settings page	Default	Description
Type= -1	[Station]	0 (all releases), 1 (Early legacy releases), 2 and 3 (from version 1.7.0), 4 (from version 1.7.12), 5 (from version 1.8.0), 6 (from version 1.8.3), 7 (from version 1.9.1), 8 to 10 (from release 1.9.2), 11 (from a MX beta build), and 12 (from release 3.2.0)	Station Settings → General Settings	Station type	-1 (not yet defined)	Drop-down -1 = "Select Station", shown before a selection from those below is made 0 = Davis Vantage Pro station 1 = Davis Vantage Pro2 or Vue station 2 = Oregon Scientific stations and similar re-badged stations (Huger, Radio Shack etc) which have a serial port connection and have wireless connection (e.g. WMR-928 station) 3 = Oregon Scientific stations and similar re-badged stations (Huger, Radio Shack etc) which have a serial port connection and have wired connection (e.g. WM-918 station) 4 = Reading from file EasyWeather.dat (using EasyWeather software version 6.2, or earlier, running continuously with Cumulus). Fine Offset weather stations that record Solar and UV measurements output to EasyWeatherPlus.dat file when Easyweather software version 6.x is running. This has the same fields as easyweather.dat, plus two extra fields for Solar and UV data at the end, and so Cumulus can understand the fields you must also have LogExtraSensors=1 set. NOTE: You can also use Type=4 if you want to run Cumulus with reduced functionality without a weather station attached, to view historical observations. A full set of (historic) files in the data subfolder copied from a system with a weather station attached is needed, but in this case, the EWFile= attribute should be at its default of not having any filename value. 5 = Fine Offset, Maplin, Chas Olsen, MyDEL, Nevada, Watson, Tycon Power, Aercus, etc as defined in Fine Offset section in Supported_Devices article (without solar measurement sensors (with or without solar recharging)) 6 = For all La Crosse WS23xx models e.g. WS2300 7 = Fine Offset/Watson/MyDel etc with Solar Sensors as defined in Fine Offset with UV/Light sensor in Supported_Devices article. 8 = Oregon Scientific stations and similar re-badged stations (Huger, Radio Shack etc) using WMR100-200_Protocol e.g. WMR100 9 = Oregon Scientific stations and similar re-badged stations (Huger, Radio Shack etc) using WMR100-200_Protocol e.g. WMR200 10 = Instromet (with optional extra solar sensors or without) 11 = Davis WLL 12 = Ecowitt GW1000 and Froggit DP1500 (and any equivalents) Selection made here determines what MX sections appear on the Station Settings page
Model=	[Station]	Early legacy version	Station Settings → General Settings	Station model	(empty)	The weather station model description that you want output by the web tag <#stationtype>

Airlink

The details in this sub-section need to be checked by someone who uses the relevant hardware.

Introduced Release
File Section is [AirLink]
Not Shown on Settings page?

IsWllNode=0 WLv2ApiKey= WLv2ApiSecret= AutoUpdateIpAddress=1 In-Enabled=0 In-IPAddress=0.0.0.0 In-WLStationId=-1 In-Hostname= Out-Enabled=0 Out-IPAddress=0.0.0.0 Out-WLStationId=-1 Out-Hostname= AQIformula=0

Parameter Line Entry	Shown on Settings page?	MX Section	Label on Settings page	Default	Description

Davis

Two Wiki sub-sections, that need to be checked by by somebody who uses the relevant functionality:

Davis VP/VP2/Vue

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

This table does not yet have all details in it.

Introduced for legacy Cumulus
File Section is [Station]
Only "Shown on Settings page" if either "Type=0" or "Type=1"

Parameter Line Entry	Default	Description
[Station]		Section name - the following parameters appear in Station section
VP2SleepInterval=500	500 (milli-seconds)	the period which Cumulus waits between reads of the data from Davis stations, the value is in milliseconds. if you suspect that data is being missed, reduce number For VirtualVP users, tests revealed that VP2SleepInterval = 1100 seems to work the best. It updates every two seconds with few exceptions.
VPClosedownTime=x	(default not yet documented)	x is the number of seconds after the start of the re-connect attempts that you want the program to close itself
DavisCalcAltPress=1	1	Davis stations calculate Sea Level Pressure (SLP) from Station Pressure (SP) using a formula based on temperature, humidity, and altitude CWOP require 'Altimeter Pressure' (AP) to be uploaded, i.e. a value calculated simply using altitude. 0 = Use SLP supplied by Davis 1 = Convert the SP Davis supplies to AP using the altitude you have supplied.
SyncDavisClock=0	0	When set, at Cumulus start-up and at a fixed time (default 04:00, see next parameter) each day, Cumulus will set the Davis VP/VP2 clock to within a minute of the same time as the PC. (From build 3015 for MX). 0 = Disabled, default (as deselected on the Station Configuration Screen) 1 = Enabled, ensures that when Cumulus asks the station for data since time X, both recognise X!
ClockSettingHour=4	4	Controls what hour of the day the SyncDavisClock activity will take place if it is enabled. 4 = 04:00 (default value) 0-23 = 00:00 to 23:00
VP2ConnectionType=1		Weather station connection type 0 = serial (see next parameter to specify COM port) (1 = usb - setting no longer available on screen, remains as default in cumulus.ini for those not using a Davis) 2 = TCP/IP (see later parameters to specify ports) Default is type 1, i.e. neither option on screen selected, so if you use a Davis you must select either serial or TCP/IP.
VP2TCPPort=22222	2222	Communications port used if VP type has TCP/IP selected.
VP2IPAddr=0.0.0.0	0.0.0.0	Weather station IP address if VP type has TCP/IP selected.
VP2PeriodicDisconnectInterval=0	0 (disable)	When the clock minute changes, Cumulus stops the current stream of data from the console, disconnects, waits for the specified number of milliseconds, to allow the Weatherlink IP to briefly connect to the Davis Weatherlink site. Cumulus then attempts to reconnect. Set it to zero to disable, if you are not using the Weatherlink site.
LogExtraSensors=0	0	This is set in the Settings block on the Station settings screen off the configuration menu. Set this to 1 if you have additional sensors (e.g. a Davis Leaf Wetness probe) to make Cumulus read, display, and log the readings from the sensors. You don't select this for Solar/UV sensors.
UseDavisLoop2=1	1 (use Loop2)	The current MX code uses LOOP2 for two purposes. First, it uses the 'peak 10-minute gust' value, to avoid the problem where a gust might be missed, and secondly it uses the 'absolute pressure' value to make calculation of 'altimeter pressure' easier and more accurate. This is mainly used if you upload to CWOP. 1 (default) = Cumulus MX will use the LOOP2 packet for Davis Weather Stations by default. The LOOP2 packet is supported on the VP2 with firmware version 1.90 or later, and on the Vue. 0 = Select this if you have a Vantage Pro (i.e. the original 'VP1'), or a VP2 with pre-1.90 firmware, or if you are using Virtual VP, none of these support the LOOP2 packet. Without this setting, Cumulus will revert to calculating the 10-minute gust value itself from the individual wind speed readings, but it will not currently attempt to calculate altimeter pressure correctly, it will simply use the sea-level pressure instead. This is likely to be an issue if you are at high altitude and you upload to CWOP using Cumulus MX.
DavisIPResponseTime=500	500	The length of time in milliseconds which Cumulus waits to allow a response from the console to a command (i.e. a request for any kind of data) from an IP logger, see Cumulus MX forum where times up to 2000ms are suggested.
ForceVPBarUpdate=0	0 (normal)	Added in build 3042 (January 2017). The default (value=0) is to assume standard barometer updates on Davis stations. Set to 1, by adding ForceVPBarUpdate=1 in [Station] section to force more frequent barometer updates on Davis stations. Steve says "Having checked the code, I see it asks for 20 packets from the 'LOOP2' if the barometer forcing is on, otherwise it stops receiving LOOP data after 50 packets". Note that ForceVPBarUpdate=1 is only useful on very old versions of the console firmware.
DavisIncrementPressureDP=0	1	(from version 3.0.0 build 3042) 0= Pressure values shown to 1 decimal places when reported in mb/hPa, shown to 2 decimal places for inHg 1= Pressure values shown to 2 decimal places when reported in mb/hPa, shown to 3 decimal places for inHg
VPrainGaugeType=0	1	Specifies the units selected on your Vantage Pro Rain Gauge. 0 = Metric Rain Adapter fitted, a 0.2mm gauge 1 = Imperial gauge without adapter, a 0.01" gauge. Note that if the units you choose for rainfall do not match your rain gauge type, conversion rounding errors will then occur.
DataLogging=0	0	(Build 3018 onwards). 0 (default) = Cumulus MX will not add extra logging. 1 = To add extra logging to the diags file for data received from Davis stations. Use this with care, the log will get very large. I've also added some more diagnostics to try to find the cause of the problem where data stops being read from Davis stations. Debug logging is required to be turned on. (Build 3022 onwards).
AutoUpdateIpAddress=1	1	default = 1, set to 0 to switch off the WLL autodetection of IP address. This is a workaround for a WLL firmware bug that does not update the IP address when it changes using DHCP.
ZeroConfig	(default not known)	set this on station settings screen; to enable/disable the entry/update of the stations IP address via auto-discovery

Davis WeatherLink Live

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

This table has not been populated yet

Introduced in a MX beta build
File Section is [WLL]
Only "Shown on Settings page" if "Type=11"

Parameter Line Entry	Label on Settings page	Default	Description
[Station]			Section name - the following parameters appear in Station section

EasyWeather (Reading File instead of connecting to a Weather Station)

This sub-section is based on what applied for the legacy software, assuming nothing has changed for MX.

Introduced in a Legacy version
File Section is [Station]
MX Section is "EasyWeather File Settings"
Only "Shown on Settings page" if "Type=4"

Parameter Line Entry	Label on Settings page	Default	Description
EWInterval=10	File Read Interval	10 (minutes between new line becoming available in file)	Cumulus needs to know how often to read a new record from the easyweather.dat file. Enter any number in box. 0= Default, meaning not applicable n= any positive decimal value representing Easyweather version 6.2, or earlier, logging interval in minutes (used for reading single latest observations from Easyweather software output). Note to specify seconds, use decimal minutes, e.g. 30 seconds = 0.5
EWFile=	Filename	(empty)	* Full file path/name for Easyweather.dat or EasyWeatherPlus.dat (empty) (i.e. attribute and equals sign, but no value) Note: If you want to run Cumulus without an attached weather station (because your station has a fault or because you have a second PC), it is possible to run Cumulus with station Type=4 but with the default of no file specified in this parameter. The full Cumulus directory structure and its files including those in the data sub-directory are needed (kept from when your station was working or copied from the PC with the station). Although only the old observations can be accessed, (no new ones are being added), this does allow analysis of the old observations via all Cumulus features See FAQ here for reduced functionality using Cumulus 1 in this way.
EWminpressureMB=900	Minimum Pressure Value	900	Cumulus will ignore all pressure readings from the station that are less than this value (units are always hPa/millibars)
EWmaxpressureMB=1200	Maximum Pressure Value	1200	Cumulus will ignore all pressure readings from the station that are greater than this value (units are always hPa/millibars)
EWMaxRainTipDiff=40	Rain Tip Difference	Default=30 tips in Cumulus 1, MX default is 40 tips	This configurable threshold is the maximum feasible amount of rain between updates (i.e. within 48-seconds on Fine Offset stations without solar, 60 seconds on those measuring solar), set in units of count of tips. For standard Fine Offset rain gauges, each tip represents 0.3mm, so 30 tips are equivalent to 9 mm, or just over a third of an inch in 48 seconds. This setting affects rain rate, rain last hour, rain so far today (and what is recorded in today.ini/dayfile.txt), but does not affect the web tag <#r24hour>.
EWpressureoffset=x.y	Pressure Offset	9999	The pressure that Cumulus MX processes is equal to what read in the file plus the value set for this parameter. Normally used to convert the station pressure to the equivalent Sea Level Pressure.

Ecowitt GW1000 and Froggit DP1500 (and any equivalents) specific

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

An Ecowitt user needs to check/update this sub-section, it is understood significant changes are included in 3.12.0 beta builds, but the forum does not give away any details

Introduced in release 3.2.0
File Section is [GW100]
MX Section is "Ecowitt GW1000 Settings"
Only "Shown on Settings page" if "Type=12"

Parameter Line Entry	Label on Settings page	Default	Description
AutoUpdateIpAddress=1	Auto-discovery	1 (selected)	Should MX attempt to discover IP address 0=Disable 1=Enable
IPAddress=	IP address	(no default)	stores the IP address of your GW1000 WiFi logger
MACAddress=	MAC addresss	(no default)	Populated by MX when auto-discovery enabled

Fine Offset Stations

Introduced in a Legacy version
File Section is [Station]
MX Section is "Fine Offset Settings"
Only "Shown on Settings page" if either "Type=5" or "Type=7"

Parameter Line Entry	Introduced	Shown on Settings page?	MX Section	Label on Settings page	Default	Description
FOReadAvoidPeriod=3	MX release ??	Only if Fine Offset selected	Station Settings → Fine Offset Advanced Settings	Read Avoid Period	3 (seconds)	If previous setting enabled, MX will avoid reading the circular memory from the number of seconds specified before it expects Fine Offset to be writing to the circular memory, to the number of seconds specified after it expects Fine Offset to be writing to the circular memory (One issue is that Fine Offset will move from one position to the next position in the circular memory, at the Fine Offset Logging Interval, but will delay this move by up to one minute, if the existing memory position is actually being updated by a read from the sensors and normally those updates happen every 40 seconds for non-solar sensors, and every 60 seconds for solar sensor)
??	MX release ??	Only if Fine Offset selected	Station Settings → Fine Offset Advanced Settings	Set the Fine Offset Logger interval to match Cumulus MX interval	0 (disabled)	Simple tick or not - labelled as "Experimental - use with caution" Tick (value shown as 1 in Cumulus.ini) for MX to attempt to "update the Davis interval" (I said copy and paste was used from Davis section!) to match the interval MX is using. Don't tick (value shown as 0 in Cumulus.ini) for no effect on your weather station
FineOffsetReadTime=150	MX release ??	Only if Fine Offset selected	Station Settings → Fine Offset Advanced Settings	Request/Read Delay	150 (milliseconds)	Adjust time (in milliseconds) between request for read, and actual attempt to read data via USB
ProductID=-1	MX release ??	Only if Fine Offset selected	Station Settings → Fine Offset Advanced Settings	USB Product Id (PID)	-1 (default setting)	Advanced setting if you don't want to leave it to MX to find your HID
SyncFOReads=0	Legacy Cumulus	Only if Fine Offset selected	Station Settings → Fine Offset Settings	Synchronise Reads	0 (disabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to attempt to work out when your Fine Offset is writing data to the console log, so that MX does not read the Fine Offset circular memory when it is being updated Don't tick (value shown as 0 in Cumulus.ini) for MX to read the Fine Offset circular memory whenever it next wants data The parameter was added for legacy releases, to try to reduce the occurrence of "lock-up" issues. MX uses a different way to interrogate Fine Offset stations, originally ticking this could result in more reads being skipped, than actually processed, potentially updating just a few times a day, so it was best disabled! The MX code relating to this parameter was rewritten 1n 3.11.0, but the developer labels this as an "attempt", so it may still be best to try to manage without enabling this setting
VendorID=-1	MX release ??	Only if Fine Offset selected	Station Settings → Fine Offset Advanced Settings	USB Vendor Id (PID)	-1 (default setting)	Advanced setting if you don't want to leave it to MX to find your HID

Instromet Settings

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

The following table has some gaps to fill in, needs a contributor who uses this type of weather station

Introduced in a Legacy version
File Section is [Station]
MX Section is "Instromet Settings" or "Instromet Advanced Options" as indicated
Only "Shown on Settings page" if either "Type=5" or "Type=7"

Parameter Line Entry	MX Section	Label on Settings page	Default	Description
ComportName=xxxxxx	Station Settings → Instromet Settings	Serial port name	/dev/ttyUSB0 (on Linux), COM1 (on Microsoft Windows)	Only required if your station is connected via a real, or virtual, serial port
ImetBaudRate=19200	Station Settings → Instromet Settings	Serial Baud Rate (DavisBaudRate)	19200	Some ?older? Instromet loggers operate at 115200, if you have one of these older loggers you will need to reset this value
"SyncDavisClock=0" and "ClockSettingHour=4"	Station Settings → Instromet Advanced Options	"Sychronise Station Clock" and "Clock sync hour"	Tick box not selected, data box set to 4	Note despite the name of the parameter within 'Cumulus.ini', this does apply to Instromet stations. Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to attempt to sychronise the Instromet Station Clock with your computer time. This ensures that when Cumulus asks the station for data since time X, both recognise X as representing same time! Don't tick (value shown as 0 in Cumulus.ini) if you don't want MX to attempt to keep station clock in line with computer clock Box taking an integer The hour of the day when, if enabled, Cumulus will set the Instromet clock to within a minute of the same time as the computer. This will happen at a default time of 04:00 each day, (4 a.m.) unless the setting box is edited
ImetUpdateLogPointer=1	Station Settings → Instromet Advanced Options	Update logger pointer	1 (enabled)	Simple tick or not Tick (value shown as 1 in Cumulus.ini) for MX to update the memory pointer to the last record after every 30 data reads Don't tick to disable this action
ImetWaitTime=500	Station Settings → Instromet Advanced Options	Delay between sending data read commands	500	Specifies the time in milliseconds that Cumulus waits after one read, before it does the next read from an Instromet station. According to the specification, 500 ms is the absolute maximum time that the station should take to respond to any command. For Cumulus 1, the default was 200 milli-seconds, so you might try that too.
ImetReadDelay=500	Station Settings → Instromet Advanced Options	Delay after sending a command before trying to read data from the serial port	500	Specifies the time in milliseconds that Cumulus allows after sending a command before it tries to read data on the serial port. According to the specification, 500 ms is the absolute maximum time that the station should take to respond to any command. For Cumulus 1, the default was 200 milli-seconds, so you might try that too.

LaCrosse stations

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

Do you understand how MX works?
Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
Does any page need a section for novices, so they don't need to read more technical information further down that page?
Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
You will find help on how to contribute to this wiki at How to Edit.
If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

The following table has some gaps to fill in, needs a contributor who uses this type of weather station

Parameter Line Entry	Shown on Settings page?	File Section	Introduced	MX Section	Label on Settings page (mostly in Alarm column)	Default	Description
LCMaxWind=X	Shown only if La Crosse was selected as station type	[Station]	3.12.0	Depends on release: (Version 1.8.8 Build 874 to release 3.11.4) Need to edit manually in file directly (Release 3.12.0 onwards) Station Settings → Common Options → Advanced Options	La Crosse max wind speed	???	It is setting for the La Crosse max wind speed, where X is the maximum (before calibrated by any definitions in Offsets) wind speed in m/s that you want to allow. The value you supply should be in metres/second, regardless of what wind unit you are using in Cumulus

It is assumed that most parameters remain same

Oregon Scientific WM918/WMR928 Settings

The Oregon Scientific code has not changed since the earliest beta MX (3.0.0) builds based on moving compiled code from Cumulus 1.

It appears very few current Cumulus users own these obsolete models, so all these settings have to be added directly into the file, you can't edit them in the admin interface, and they will be missing from any configuration file created by any MX release.

Introduced for legacy Cumulus, and unchanged by MX
File Section is [Station], these settings need to be manually entered into file below that section heading

Parameter Line Entry	External to MX edit	Default	Description
[Station]			Section name - the following parameters appear in Station section
Humidity98Fix=0	Stop MX and add this into file	0 (disable)	Applies to weather station types that never report more than 98% relative humidity. 0 = Disabled (default) 1 = Enabled, humidity displayed and recorded as 100% if your sensor registers a relative humidity of 98%. Normally only useful for Oregon Scientific stations.
LogExtraSensors=0	Stop MX and add this into file	0 (disable)	This setting determines whether MX looks for readings from extra temperature probes etc. 0=Disabled (default) 1= Enabled - Used for Oregon Scientific WMR-928 and similar stations if you have additional sensors (e.g. another temperature probe) to make Cumulus read, display, and log the readings from those sensors. You don't use this for Solar/UV sensors..
WMR928TempChannel=N	Stop MX and add this into file	(by default no extra sensors)	for WMR-928 stations (and other serial stations using the same protocol, eg WMR-968) to use an 'extra' channel (see previous parameter) as your main temperature sensor, set N to the required channel
WMR200TempChannel=N	Stop MX and add this into file	(by default no extra sensors)	for WMR200 stations (and any other Oregon Scientific USB stations which work with Cumulus, e.g. WMR100) to use an 'extra' channel as your main temperature sensor, set N to the required channel

Units, Derivative Options, and Decimal Places

For altitude units, please see #Location.

File Section is [Station]
Edit on Station Settings page (except where indicated in bold as another page)

Parameter Line Entry	Introduced	MX Section	Label on Settings page	Default	Description
AirQualityDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Air Quality decimals	1 (displayed as blank)	Number of decimal places for all outputs
AvgBearingMinutes=10	Legacy Cumulus	Common Options → Advanced Options (Here be dragons!)	Average Bearing Minutes	10 (minutes)	This parameter's value is the number of minutes over which Cumulus calculates (by treating the wind as a vector and taking into account the speed as well as direction) its average bearing
AvgSpeedMinutes=10	Legacy Cumulus	Common Options → Advanced Options (Here be dragons!)	Average Speed Minutes	10 (minutes)	This parameter's value is the number of minutes over which Cumulus averages out reported current wind speeds
CalculatedDP=0	Legacy Cumulus	Common Options	Calculate dew point	Unticked (shown as 0 in Cumulus.ini)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then Cumulus will calculate dew point from temperature and humidity supplied by station Don't tick (value shown as 0 in Cumulus.ini) action depends on Calibration settings If Cumulus has non-default multiplier and/or offset settings for temperature or humidity, Cumulus will calculate dew-point. This avoids the restriction in the Oregon Scientific stations where the dew point can never be below freezing point. If station provides dew point, then that will be used provided no multiplier/offsets have been specified for temperature or humidity
CalculatedWC=1	Legacy Cumulus	Common Options	Calculate wind chill	Unticked (shown as 0 in Cumulus.ini)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then Cumulus will calculate wind chill from temperature and wind speed Note that there is a maximum temperature, and minimum wind speed, for Cumulus to make the calculation, see Wind_chill page Don't tick (value shown as 0 in Cumulus.ini) action depends on other items: If Cumulus has non-default multiplier and/or offset settings for temperature or wind speed, Cumulus will calculate wind chill If station does NOT make a wind chill value available to Cumulus, Cumulus MX reports an error if you have not ticked this setting, (that is different to how the setting worked with the legacy software). If station provides wind chill, then that value will be used provided no multiplier/offsets have been specified for temperature or wind speed.
ChillHourSeasonStart=	Legacy Cumulus	Chill Hours	Chill Season Starts	Default depends on release (up to 3.11.4) 10 = October (from 3.12.0) 4 in Southern hemisphere, 10 in Northern hemisphere	The value to enter is the month number (1=January, 12=December) and the Cumulative Chill Hours Count is reset to zero on the first of the selected month
ChillHourThreshold=	Legacy Cumulus	Chill Hours	Chill Hours	Default depends on Temperature Units Either 45 degrees Fahrenheit (equivalent to 7.22 ^oCelsius) Or 7 degrees Celsius (equivalent to 44.6 ^oFahrenheit)	Chill Hours are incremented by the number of (fractional) hours that the air temperature is below the threshold. In practice, Cumulus simply detects if the current temperature is below the threshold and adds an increment equivalent to the (interval) time passed since the last temperature reading. You can put in any value you want, with a decimal place if required Some people have put in the freezing-point temperature (0^oC or 32 ^oF) and they relabel "chill hours" to "frost hours"
CloudBaseInFeet=0	Legacy Cumulus	(As at 3.11.4, can only adjust in the file)		0 (default in MX is metres)	Select units used for reporting theoretical cloud base: 0 = metres (default if file created by MX) 1 = feet (default if file created by legacy software)
ErrorLogSpikeRemoval=1	Legacy Cumulus	Calibration Settings → Final tick box	Log spike and limit violations to error log	1 (default in MX is enabled)	Log spike and limit violations to error log (in MX this is in MXdiags folder): 1 = do log (default if file created by MX) 0 = don't log (default if file created by legacy software)
HourlyForecast=1	Legacy Cumulus	Forecast	Update forecast hourly	1 (default in MX is enabled)	When Cumulus derives its Zambretti forecast Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will derive a Zambretti forecast just once an hour, on the hour Don't tick (value shown as 0 in Cumulus.ini) to derive a forecast every time MX does a process of the pressure reading
Humidity98Fix=0	Legacy Cumulus	Common Options	Max humidity	0 (disable)	For any weather station that never reports a relative humidity greater than 98% Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then if weather station reading is 98%, process that as 100% for all outputs from MX Don't tick (value shown as 0 in Cumulus.ini) to always report what weather station reports for relative humidity
PeakGustMinutes=10	Legacy Cumulus	Common Options → Advanced Options (Here be dragons!)	Peak wind gust time	10 (minutes)	MX waits until a gust has been measured for number of minutes specified by value of parameter, before checking whether previous gust extreme record have been exceeded
PressDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Pressure decimals	Default depends on Pressure Units (displayed as blank) default is 1 if units are hPa or mb default is 2 if units are inches of mercury	Number of decimal places for all outputs
PressureUnit=1	Legacy Cumulus	Units	Pressure	Depends on release: Legacy to 3.11.4: 0 (mbar) 3.12.0 onwards: 1 (hPa)	Drop-down: 0 = millibar (mb) 1 = hectoPascals (hPa) 2 = inches of mercury (in Hg)
RainDayThreshold=	Legacy Cumulus	Common Options → Advanced Options	Rain day threshold	Default is -1 which depends on Rainfall Units AND station type -1 = normally 0.2 if units are millimetres -1 = normally 0.01 if units are inches Otherwise enter a value in your selected units	For derivatives like count of consecutive wet/dry days, any daily rainfall less than this threshold will be ignored. (If rainfall is measured in tips, usually set to just over one tip, as first tip of day might be result of less that one tip accumulated on earlier days or because of dew)
RainDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Rainfall decimals	Default depends on Rainfall Units (displayed as blank) default is 1 if units are millimetres default is 2 if units are inches	Number of decimal places for all outputs
RainSeasonStart=1	Legacy Cumulus	Annual Rainfall	Start of rainfall season	1 (Jan)	Drop-down 1 = January 2 = February 3 = March ... 9 = September 10 = October 11 = November 12 = December Added in late 2010 because Cumulus users in Israel said they do not total rainfall from January. It was welcomed by people outside Israel, it turned out growers are often interested in a growing season rainfall total
RainUnit=0	Legacy Cumulus	Units	Rain	0 (mm)	Drop-down: 0 = millimetres 1 = inches
RoundWindSpeed=0	Legacy Cumulus	Common Options	Rounding of wind speed	0 (no)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will round all the wind speeds it reports to nearest integer Don't tick (value shown as 0 in Cumulus.ini) then MX will report wind speeds to the precision defined in "WindSpeedDecimals" parameter
SunshineHrsDecimals=2	Release 3.8.0	Units → Advanced Options (Here be dragons!)	Sunshine hours decimals	2 (displayed as blank)	Select a number of decimal places to overwrite the default
TempDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Temperature decimals	1 (displayed as blank)	Select a number of decimal places to overwrite the default
TempUnit=0	Legacy Cumulus	Units	Temperature	0 (^oC	Drop-down: 0 = Celsius 1 = Fahrenheit
UseCumulusForecast=0	Legacy Cumulus	Forecast	Use Cumulus Forecast	0 (disabled)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then Cumulus will generate a simple weather Zambretti forecast, if your station does not supply a forecast, or as an alternative to the one supplied by your station. Please see Forecast_webtag for details. Don't tick (value shown as 0 in Cumulus.ini) then MX will not do any forecasting, so it will return "not available" unless your weather station provides an alternative forecast
UseCumulusPresstrendstr=0	Legacy Cumulus	Common Options	Cumulus pressure trend names	0 (depends on weather station type)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will generate the name for the current pressure trend, e.g. "Falling", "Rising quickly" etc, instead of the one supplied by your station. The names used are those in the UK Shipping Forecast, but can be modified using strings.ini. Don't tick (value shown as 0 in Cumulus.ini) then effect depends on whether your weather station supplies pressure trends If your station does supply pressure trends, then MX will use those If your station does not supply pressure trends, then MX will generate the name for the current pressure trend, e.g. "Falling", "Rising quickly" etc, instead of the one supplied by your station. The names used are those in the UK Shipping Forecast, but can be modified using strings.ini.
UseSpeedForAvgCalc=0	Legacy Cumulus	Common Options	Use speed for average calculation	0 (disable)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will use what the weather station supplies as "wind speed" to calculate the average wind speed. Don't tick (value shown as 0 in Cumulus.ini) then MX will use what the weather station supplies as "latest wind speed" to calculate the average wind speed Please see Wind_measurement#Weather_Stations_and_Cumulus for more details.
UseZeroBearing=1	Legacy Software	Common Options	Use bearing zero when calm	1 (enable)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will report a wind bearing of zero when the wind is calm Don't tick (value shown as 0 in Cumulus.ini) then MX will continue to report the last wind bearing when the wind stops blowing
UVDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Ultra Violet decimals	1 (displayed as blank)	Select a number of decimal places to overwrite the default
Wind10MinAverage=0	Legacy Cumulus	Common Options	Calculate average wind speed	0 (disable)	Simple tick or not: Tick (value shown as 1 in Cumulus.ini) then MX will calculate an average wind speed (over ten minutes) as defined by "UseSpeedForAvgCalc" parameter Don't tick (value shown as 0 in Cumulus.ini) then MX will use whatever the weather station provides as an average wind speed Please see Wind_measurement#Weather_Stations_and_Cumulus for more details.
WindRunDecimals=1	Release 3.9.2	Units → Advanced Options (Here be dragons!)	Wind run decimals	1 (displayed as blank)	Select a number of decimal places to overwrite the default
WindSpeedAvgDecimals=1	Release 3.8.3	Units → Advanced Options (Here be dragons!)	Wind speed average decimals	1 (displayed as blank)	Select a number of decimal places to overwrite the default
WindSpeedDecimals=2	Release 3.8.3	Units → Advanced Options (Here be dragons!)	Wind speed average decimals	2 (displayed as blank)	Select a number of decimal places to overwrite the default
WindUnit=0	Legacy Cumulus	Units	Wind	Default depends on release: Legacy to 3.11.4: 0 (m s^-1) 3.12.0 onwards: 2 (km hr^-1)	Drop-down: 0 = metres per second 1 = miles per hour 2 = Kilometres per hour 3 = Knots (nautical miles per hour or kts)
YTDrain=0	Legacy Cumulus	Annual Rainfall	Year-to-date amount	0 (displayed as blank)	Enter the amount of rainfall to be added to the calendar year in next parameter (used when start using Cumulus in middle of year)
YTDrainyear=	Legacy Cumulus	Annual Rainfall	Year to which year-to-date amount applies	(displayed as blank)	Enter a 4 digit year: Legacy Releases (1.7.12 5 July 2008) and MX up to 3.11.4 (build 3133 25 May 2021): The year-to-date amount in previous parameter is added to the current (seasonal) rain if the year specified in this parameter matches the current year. If your rain season starts in January (default) then set this to the calendar year when you first use Cumulus (in a particular location). If your rain year starts in any other month, set this to this year if your first season starts this year, and set this to last year if your second season has started and you don't want the previous value added to your second season From Release 3.12.0 (?? July 2021), the current calendar year is compared against (current month - season start month + 1) year, so you enter the year in which your first season starts (be that last calendar year or this calendar year)