Cumulus.ini: Difference between revisions

4,758 bytes added ,  13 September 2022
m
Minor clarifications in response to forum post
m (Minor clarifications in response to forum post)
 
(63 intermediate revisions by 4 users not shown)
<big>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.</big>
 
{{Template:WorkInProgressBanner}}
=Purpose of Cumulus.ini file=
 
This is a text file containing initialization parameters. {{Template:Version badge Mx}}This page covers those used by the Cumulus MX software applicationapplica3.2.0 to 3.5.4tion.
 
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".
* 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"?==
 
= Why does this Wiki now contain multiple pages describing "Cumulus.ini"?=
 
[[Category:Configuration Files]]
MX has been developed very dramatically by Mark Crossley:
# There were minor differences between the legacy '''cumulus.ini''' (for versions 1.x.y, ending inwith 1.9.4) [[Cumulus.ini (Cumulus 1)|the cumulus.iniwith documentation has been moved tonow 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, [[Cumulus.ini (MX 3.0.0 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, <big>the decision was taken to abandon maintaining the page previously called "Cumulus.ini", and start again with a brand new empty page!</big>
 
 
All the pages, previously called "Cumulus.ini", can be found from the owning [[:Category:Configuration Files|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.
All the pages, previously called "Cumulus.ini", can be found from the owning [[:Category:Configuration Files|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.
 
You will also note that this page does not cover all settings in detail, and find some links to further pages within some sections below
 
==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 [https://github.com/cumulusmx/CumulusMX/releases/download/b3141/CumulusMXDist3141.zip here] and runs that release for a while before upgrading to the latest release [https://github.com/cumulusmx/CumulusMX here].
 
== Simplifications ==
 
Using theThe MX configuration is simplervery thatdifferent to that used by the legacy software. Since MX requires far more parameters as it has far more optional functionality, than the developerlegacy hadsoftware, to devise a way to make it easier for those usingtherefore MX torequires quicklyfar assignmore the settings that might be best for those newparameters to Cumulustailor toall getthese thefunctionality software working without needing to understand all the settingsoptions.
 
The file is read into Internal Variables as Cumulus starts, and those variables are written back into the file when any settings are changed.
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.
 
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 [[Cumulus.ini_(Cumulus_1)#Configuration_File_names|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 theany "File section" you were goingintended 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!
 
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.
 
 
 
This Wiki page does not explain how to start using MX, please see [[MX on Linux]], [[MX on Windows OS]], and [[MX Administrative Interface]] as appropriate.
 
The key fact relevant here is that no Cumulus release distribution contains a '''Cumulus.ini''' file. So when you first use the software, you will need to use the [[MX_Administrative_Interface#Changing_Settings|admin interface]] to enter all settings (some have defaults that might be right for you) as described later in this page, and that will lead to creation of the main configuration file.
 
If you later 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 below)
 
Furthermore, at the end of each (meteorological) day, MX creates a back-up in the [[Backup folder|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.
 
 
=How this Wiki page classifies settings=
 
Whenever MX is restarted, it reads the latest ''Cumulus.ini'' and if it exists [[Strings.ini|strings.ini]] (briefly mentioned below); from these one (or two) file(s), it learns the configuration that you want it to use.
 
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.
 
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.
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.
 
<big>Please see [[First Run of MX]] for how to set up settings when you first use MX.</big>
==First run of 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)
# If you start Cumulus MX without a configuration file, and you have a screen attached so you can see the output from the engine, it will show this: [[File:MX first start.PNG]]
# As you can see, it is running, but it does not know what station type, so it cannot connect to it, and will not do anything more.
# At this stage, MX creates a very basic Cumulus.ini with the default settings (shown below).
#Open the [[MX Administrative Interface|admin interface]], and select the station settings if necessary: [[File:MX_station_settings.png|800px|center]]
# At the very minimum, you must select a station type and units (as shown in image here)
# Optionally, move down the page, entering more settings,
#* The settings that are displayed to you vary depending on the station type you have selected (and the particular MX release), so there is not a screenshot to show you the other settings for your station type.
# Optionally, move to other settings pages accessed from the menu seen in the image, these cover the optional functionality of MX, so the pages you need to visit depends on what functionality you wish to use.
# Optionally, use [[Samplestring.ini]] file as a guide to create a [[Strings.ini|strings.ini]] file (look up the cross reference if you want to do this now, but you can leave it to later) where you can tailor a number of texts that Cumulus produces.
#* The advantage of creating your '''strings.ini''' file now, is that it is read when MX starts, and we will shortly restart MX.
# Closing MX is the action that will create the main configuration file.
# MX must be stopped correctly, because it has to do a number of actions after it receives a request to close:
#* If you have a screen attached to the device running the MX engine, you can click in that screen and terminate Cumulus MX by typing '''C''' while holding down the control key (or equivalent if you are using an apple mac).
#* If you are connecting to MX from a remote device, then type into that remote session the control '''C'''.
#* Otherwise do whatever is needed to end the MX executable on your installation.
# Restart Cumulus MX, it will read your new settings (in '''Cumulus.ini''' and the optional '''strings.ini''') on re-starting, it will find the weather station, and start reading the weather data from it. On this first access to your weather station, it will not read any archive data (there is a way to modify [[today.ini]] so it can read what is in the separate logger), but from now (until you stop it) it will read (and from time to time log) the live data while MX remains running.
 
==Where do I change 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 folder|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?==
 
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=
|}
 
== Alarms (and Email Settingsemails) ==
 
 
{{Template:WorkInProgressBanner}} Please will somebody who uses this functionality complete this section, alarms have changed dramatically since 3.8.0 with introduction of email messages
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | File Section
!style="width:100px" | Introduced
!style="width:100px" | MX Section
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:300px" | Description
|-
|
|
|
|
|
|}
[SMTP]
Enabled=0
ServerName=
Port=587
SSLOption=1
RequiresAuthentication=0
User=
Password=
Logging=0
 
The Alarm settings seem to frequently be changed by new MX releases, so have been moved to a separate [[Alarms|wiki page]] where hopefully it will be easier for somebody to keep the content updated in future.
[Alarms]
alarmlowtemp=0
LowTempAlarmSet=0
LowTempAlarmSound=0
LowTempAlarmSoundFile=alarm.mp3
alarmhightemp=0
HighTempAlarmSet=0
HighTempAlarmSound=0
HighTempAlarmSoundFile=alarm.mp3
alarmtempchange=0
TempChangeAlarmSet=0
TempChangeAlarmSound=0
TempChangeAlarmSoundFile=alarm.mp3
alarmlowpress=0
LowPressAlarmSet=0
LowPressAlarmSound=0
LowPressAlarmSoundFile=alarm.mp3
alarmhighpress=0
HighPressAlarmSet=0
HighPressAlarmSound=0
HighPressAlarmSoundFile=alarm.mp3
alarmpresschange=0
PressChangeAlarmSet=0
PressChangeAlarmSound=0
PressChangeAlarmSoundFile=alarm.mp3
alarmhighraintoday=0
HighRainTodayAlarmSet=0
HighRainTodayAlarmSound=0
HighRainTodayAlarmSoundFile=alarm.mp3
alarmhighrainrate=0
HighRainRateAlarmSet=0
HighRainRateAlarmSound=0
HighRainRateAlarmSoundFile=alarm.mp3
alarmhighgust=0
HighGustAlarmSet=0
HighGustAlarmSound=0
HighGustAlarmSoundFile=alarm.mp3
alarmhighwind=0
HighWindAlarmSet=0
HighWindAlarmSound=0
HighWindAlarmSoundFile=alarm.mp3
SensorAlarmSet=0
SensorAlarmSound=0
SensorAlarmSoundFile=alarm.mp3
DataStoppedAlarmSet=0
DataStoppedAlarmSound=0
DataStoppedAlarmSoundFile=alarm.mp3
BatteryLowAlarmSet=0
BatteryLowAlarmSound=0
BatteryLowAlarmSoundFile=alarm.mp3
DataSpikeAlarmSet=0
DataSpikeAlarmSound=0
DataSpikeAlarmSoundFile=alarm.mp3
 
==Charts==
!style="width:20px" | Default
!style="width:600px" | Description
|-
| StartDate=
| (with warning: "Here be dragons!")
| Station Settings &rarr; 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.
|-
| 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).
|-
| 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
|-
| DataLogInterval=2
|-
| LogExtraSensors=0
| (Depends on station type) Only from Release 3.12.0
| Station settings &rarr; Common Options
| Extra sensors
* 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 &rarr; Common Options &rarr; 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
* 0 = MX will do [[MX_Basic_info#MX_End_of_Day_Process|an end of day process]] when the time (on Weather Station if it provides time) reaches midnight
* 1 = MX will do [[MX_Basic_info#MX_End_of_Day_Process|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 &rarr; Common Options &rarr; 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 &rarr; Common Options &rarr; 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
| 1 (normal)
| Tick box:
* 0 = If "Daylight Saving Time" (DST) applies in Summer, MX is to use 9 am local time
** 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
|}
 
==Database==
 
 
* Available from beta MX.
* File Section is [MySQL]
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | Shown on Settings page?
!style="width:100px" | MX Section
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:600px" | Description
|-
| CustomMySqlMinutesCommandString=
| only if "Custom Minutes Enabled"
| MySQL Settings &rarr; Monthly log file upload
| SQL command
| (blank)
| SQL to be obeyed at the interval defined in "CustomMySqlMinutesIntervalIndex"
|-
| CustomMySqlMinutesIntervalIndex=6
| only if "Custom Minutes Enabled"
| MySQL Settings &rarr; Monthly log file upload
| Interval
| 6 = 10 minutes
| Time between custom SQL uploads:
* 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)
|-
| CustomMySqlMinutesEnabled=0
| (always)
| MySQL Settings
| Custom Minutes Enabled
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the optional functionality to run SQL at a selected interval in minutes
|-
| CustomMySqlSecondsCommandString=
| only if "Custom Seconds Enabled"
| MySQL Settings &rarr; Monthly log file upload
| SQL command
| (blank)
| SQL to be obeyed at the interval defined in "CustomMySqlSecondsInterval"
|-
| CustomMySqlSecondsInterval=10
| only if "Custom Seconds Enabled"
| MySQL Settings &rarr; Monthly log file upload
| Interval
| 10 (seconds)
| Time between custom SQL uploads
|-
| CustomMySqlSecondsEnabled=0
| (always)
| MySQL Settings
| Custom Minutes Enabled
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the optional functionality to run SQL at a selected interval in seconds
|-
| Database=
| when section opened
| MySQL Settings &rarr; Server Details
| Database name
| (blank)
| The name given to the database that includes the table(s) you want to update
|-
| DayfileMySqlEnabled=0
| (always)
| MySQL Settings
| Dayfile Enabled
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the automatic upload to the table named in "DayfileTable" within the database named in "Database"
|-
| DayfileTable=Dayfile
| when "Dayfile Enabled" is ticked and the next section is opened
| MySQL Settings &rarr; Dayfile.txt upload
| Table name
| Dayfile
| Enables you to choose the name for the database table to be updated when "DayfileMySqlEnabled" is ticked
|-
| Host=
| when section opened
| MySQL Settings &rarr; Server Details
| Host name
| (blank)
| Enter the database server name or Internet Protocol address
|-
| MonthlyMySqlEnabled=0
| (always)
| MySQL Settings
| Monthly Log Enabled
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the automatic upload to the table named in "MonthlyTable" within the database named in "Database"
|-
| MonthlyTable=Monthly
| when "Dayfile Enabled" is ticked and the next section is opened
| MySQL Settings &rarr; Monthly log file upload
| Table name
| Monthly
| Enables you to choose the name for the database table to be updated when "MonthlyMySqlEnabled" is ticked
|-
| Pass=
| when section opened
| MySQL Settings &rarr; Server Details
| Password
| (blank)
| Enter the password needed to access the database server specified in "Host"
|-
| Port=3306
| when section opened
| MySQL Settings &rarr; Server Details
| Port
| 3306
| Enter the port used to access the database server
|-
| RealtimeMySql1MinLimit=0
| When section opened
| MySQL Settings &rarr; Raltime.txt upload
| Limit real time table inserts to once a minute
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the optional functionality to limit database uploads, if your real time interval has been set to less than 60 seconds
|-
| RealtimeMySqlEnabled=0
| (always)
| MySQL Settings
| Realtime enabled
| Not ticked (shown as 0 in Cumulus.ini)
| Enable the automatic upload to the table named in "RealtimeTable" within the database named in "Database"
|-
| RealtimeRetention=
| When section opened
| MySQL Settings &rarr; Raltime.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
| When section opened
| MySQL Settings &rarr; Raltime.txt upload
| Table name
| Realtime
| Enables you to choose the name for the database table to be updated when "RealtimeMySqlEnabled" is ticked
|-
| User=
| when section opened
| MySQL Settings &rarr; Server Details
| User name
| (blank)
| Enter the username associated with "Pass"
|}
 
==Debugging==
| 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 &rarr; Display Options'''
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | Introduced
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:600px" | 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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|webfiles folder]] (from release 3.10.0 onwards) for consistency with Cumulus from release 3.6.0
|}
 
 
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.'''
 
{| class="wikitable" border="1"
| The selections made on this Settings Page sub-section will place the appropriate content in the two parameters in the file
|}
 
 
==Optional Report Settings==
| NOAA Reports Settings &rarr; FTP Options
| destination folder
| Depends on release:
| (empty)
* (3.1.0 to 3.11.4) blank
| Where you want MX to use as destination folder on your FTP server
* (3.12.0 onwards) to match change in default web site script specification of '''Reports''' folder
*Leave blank and MX will use wherever has been specified in main internet settings (this fits how the default web site is designed to work)
| Specify the destination folder for file transfer to, on your FTP server
* Specify a folder relative to FTP root, and MX will upload reports to that folder instead (if you use any files from default web site, then you will need to amend the JavaScript file:
*Leave at default (for your release) and MX will work with the default web pages script supplied (at same release)
<code>let rptPath = ''; // Your path should have a trailing "/", eg. 'Reports/'</code> by putting your folder name in, an example is given for the case when “/Reports” is a sub folder off the main upload destination, note how you don’t include a leading slash, but you must add a trailing one.
* 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
* 12 Hour (value shown as 1 in Cumulus.ini)
|}
 
 
 
* File Section is [NOAA]
Rainfall equivalents of mean temperature described above
 
 
==Optional Structured Query Language Settings==
 
MX uses a software package called "MySqlConnect" to run SQL queries.
 
Since the text that appeared here was added, documenting plans for the future 3.12.0 release, there have been a number of changes, and now a future release (3.20.0) is expected to make more drastic changes. Therefore the content has been moved to a [[MySqlConnect|new "MySqlConnect" page]] where it is hoped somebody will find it easier to update the content as MX develops.
 
 
==Optional Third-party Upload Settings==
!style="width:30px" | File Section
!style="width:60px" | MX Section
!style="width:60px80px" | Action on Settings page
!style="width:20px" | Default
!style="width:600px" | Description
|-
| <pre>ID=
==Optional Web Server==
 
There are two sub-sections below, because the settings for the optional web functionality are split between '''Station Settings''' and '''Internet Settings'''.
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.
 
 
=== Display Options controlling what appears on default web pages ===
 
* File Section is '''[Display]'''
* MX Section is '''Station Settings &rarr; Display Options'''
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | Introduced
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:600px" | 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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|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 [[New_Default_Web_Site_Information|web pages]] provided in [[Webfiles folder|webfiles folder]] (from release 3.10.0 onwards) for consistency with Cumulus from release 3.6.0
|}
 
 
=== File transfer and Copy Options controlling transfer of data to default web pages ===
 
The settings listed in table below changed dramatically at both 3.10.0 and 3.12.0 releases, but they have gradually evolved throughout the development of MX.
 
FRomFrom 3.12.0, MX can optionally ''either'' '''copy''' files to a [[Your Own Server|web server you host]] ''or'' '''file transfer''' files to a [[Webspace|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
| 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
|-
| [FTP site]
| Legacy Cumulus
| FTP logging
| No
| ChangeDepends directly in file as aton release 3.11.xinstalled:
# (Releases 3.1.0 to 3.10.5) Internet Settings &rarr; &rarr; Web Settings &rarr; General Settings
# (Releases 3.11.0 to 3.11.4) Program Settings &rarr; Program General Options
# (Release 3.12.0 onwards) Program Settings &rarr; Logging Options
| (n/a)
| (n/a)
| Simple tick or not
| *0 = Disabled (default)
*1 =Tick Enabled,(value Cumulusshown willas 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
| (always)
| Internet Settings &rarr; 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
| Parameter attribute depends on release:
# AutoUpdate=0
# IntervalEnabled=1
| [FTP site]
| For respective parameter attribute:
# Legacy to 3.11.4, as deprecated in 3.12.0
# Introduced release 3.10.0, takes over from 3.12.0
| ^
| Internet Settings &rarr; Interval Settings
| Enable web update interval
| Default depends on respective attribute:
# 0 (disabled) for legacy web pages
# 1 (enabled) for new default web pages
| Simple tick or not
* Tick (value shown as 1 in Cumulus.ini) for MX to generate a timer that will permit standard interval actions
* Don't tick (value shown as 0 in Cumulus.ini) if either no web server, or no standard interval uploading required
|-
|IntervalFtpEnabled=1
| [FTP site]
| Release 3.12.0
* 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 &rarr; Common Options &rarr; 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
| (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 &rarr; 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 &rarr; Moon Image
| Image size
| ???
| Enter a size (in pixels) for the generated moon image (according to space on your web page)
|-
| Password=
| 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
* 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 &rarr; General Settings &rarr; Advanced options
*# Station settings &rarr; Common Options &rarr; 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=
| 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)
|-
| the user name for connecting to your server
|-
| UTF8encode=1
| [FTP site]
| legacy software
* (release 3.12.0 on) Internet Settings &rarr; Web Site &rarr; General Settings
| UTF-8 encoding
| Default depends on release:
| 1 (enabled)
* (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 [[Reports_folder#Encoding|'''UTF-8''' encoding]] in all [[:Category:JSON Files|.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''', and''please note that this encoding is incompatible with [[New_Default_Web_Site_Information#Installing_the_new_template_for_new_users|web pages]] included in '''webfiles''' folder.''; so if you upgrade from an earlier release, you may need to change this setting
|-
|WebcamURL=
*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 [https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=728 here for request] and see [[Cumulus.ini_(Cumulus_1)#Proxies|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==
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.
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | File Section
!style="width:100px" | Introduced
!style="width:100px" | MX Section
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:800px" | Description
|-
| SolarCalc=0
| [Solar]
| 3.13
| Station Settings &rarr; Solar
| Solar Calculation Method
| 0=Ryan-Stololzenbach
| Drop-down list:
* 0=Ryan-Stololzenbach
* 1=Bras
|-
| SunThreshold=75
| [Solar]
| 3.13
| Station Settings &rarr; Solar
| Sun Threshold (percent)
| 75
| Enter a number
|-
| SolarMinimum=0
| [Solar]
| 3.13
| Station Settings &rarr; Solar
| Solar minimum (W/m2)
| 30
| Enter a number
|-
| RStransfactorJul=0.80000000000000004
| [Solar]
| 3.14
| Station Settings &rarr; 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 &rarr; 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===
 
{| class="wikitable" border="1"
 
===Airlink===
 
The details in this sub-section need to be checked by someone who uses the relevant hardware.
 
* Introduced Release
===Davis===
 
Two Wiki sub-sections, that need to be checked by by somebody who uses the relevant functionality:
 
 
 
{{Template:WorkInProgressBanner}} This table does not yet have all details in it.
* Introduced for leagacylegacy Cumulus
* File Section is [Station]
* Only "Shown on Settings page" if either "Type=0" or "Type=1"
===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
 
===Ecowitt GW1000 and Froggit DP1500 (and any equivalents) specific===
 
{{Template:WorkInProgressBanner}} 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
 
===Fine Offset Stations===
 
 
{{Template:WorkInProgressBanner}} This table has not been populated yet
 
* Introduced in a Legacy version
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | Introduced
!style="width:100px" | Shown on Settings page?
!style="width:100px" | MX Section
!style="width:60px" | Label on Settings page
!style="width:20px" | Default
!style="width:300px" | Description
|-
| FOReadAvoidPeriod=3
| MX release ??
| Only if Fine Offset selected
| Station Settings &rarr; 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 &rarr; 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 &rarr; 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 &rarr; 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 &rarr; Fine Offset Settings
| Synchronise Reads
| 0 (disabled)
* 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
Selecting this parameter has given some problems in earlier MX builds, so the code has recently been rewritten.
|-
| FOReadAvoidPeriod=3
| 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
 
# The parameter was added for legacy releases, to try to reduce the occurrence of "lock-up" issues.
(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 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
 
 
 
{{Template:WorkInProgressBanner}}
There are a number of settings in a MX sub-section called "Fine Offset Advanced Options". These are new settings, and have not been documented yet.
 
{| class="wikitable" border="1"
|-
| VendorID=-1
!style="width:30px" | Parameter Line Entry
| MX release ??
!style="width:100px" | Shown on Settings page?
| Only if Fine Offset selected
!style="width:100px" | MX Section
| Station Settings &rarr; Fine Offset Advanced Settings
!style="width:60px" | Label on Settings page
| USB Vendor Id (PID)
!style="width:20px" | Default
| -1 (default setting)
!style="width:600px" | Description
| Advanced setting if you don't want to leave it to MX to find your HID
|-
|
|}
 
 
 
{{Template:WorkInProgressBanner}} The following table has some gaps to fill in, needs a contributor who uses this type of weather station
 
* Introduced in a Legacy version
|}
 
===WM918/WMR928 Settings===
 
===LaCrosse stations===
Oregon Scientific specific
 
{{Template:WorkInProgressBanner}} This table has not been populated yet
 
 
* Introduced for legacy Cumulus
{{Template:WorkInProgressBanner}} The following table has some gaps to fill in, needs a contributor who uses this type of weather station
* File Section is [Station]
 
 
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | LabelShown on Settings page?
!style="width:100px" | File Section
!style="width:150px" | Introduced
!style="width:100px" | MX Section
!style="width:60px" | Label on Settings page (mostly in '''Alarm''' column)
!style="width:20px" | Default
!style="width:300px" | 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 &rarr; Common Options &rarr; 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 [[Cumulus.ini_(Cumulus_1)#La_Crosse_specific:|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
{| class="wikitable" border="1"
|-
!style="width:30px" | Parameter Line Entry
!style="width:100px" | External to MX edit
!style="width:20px" | Default
!style="width:300px" | Description
|-
|Humidity98Fix=0
| Stop MX and add this into file
|
|0 (disable)
|Applies to weather station types that never report more than 98% relative humidity.
|-
|LogExtraSensors=0
| Stop MX and add this into file
|
|0 (disable)
|This setting determines whether MX looks for readings from extra temperature probes etc.
|-
|WMR928TempChannel=N
| Stop MX and add this into file
|
|(noby 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
|
|(noby 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
|}
* 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 '''Calibrationother settings'''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 will be used provided no multiplier/offsets have been specified for temperature or wind speed
** If station provides wind chill, then that value will be used provided no multiplier/offsets have been specified for temperature or wind speed.
Note that some stations (Fine Offset, for example), do not make a wind chill value available to Cumulus. For these, Cumulus always calculates it.
|-
| ChillHourSeasonStart=
| Legacy Cumulus
| Chill Hours
| (TO BE DETERMINED)
| Chill Season Starts
|
| Default depends on release
* (up to 3.11.4) 10 = October
| ChillHourThreshold=
| Legacy Cumulus
| Chill Hours
| (TO BE DETERMINED)
| Chill Hours
|
| Default depends on Temperature Units
* Either 45 degrees Fahrenheit (equivalent to 7.22 <sup>o</sup>Celsius)
| Humidity98Fix=0
| Legacy Cumulus
| Common Options
| (TO BE DETERMINED)
| Max humidity
| n/a
| 0 (disable)
| For any weather station that never reports a relative humidity greater than 98%
| RainDayThreshold=
| Legacy Cumulus
| Common Options &rarr; Advanced Options
| (TO BE DETERMINED)
| Rain day threshold
| n/a
| Default is -1 which depends on Rainfall Units AND station type
| (TO BE DETERMINED)
* -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.
 
| Rounding of wind speed
| 0 (no)
| Simple tick or not, (only applicable if any reported wind speed would otherwise include decimal places):
| Simple tick or not:
* Tick (value shown as 1 in Cumulus.ini) then MXCumulus will round all the wind speeds it reports to nearest integer
* Don't tick (value shown as 0 in Cumulus.ini) then MXCumulus will report wind speeds to the precision defined in "WindSpeedDecimals", parameter"WindSpeedAvgDecimals", and "WindRunDecimals", parameters
|-
| SunshineHrsDecimals=2
| Select a number of decimal places to overwrite the default
|-
| WindSpeedAvgDecimals=1
| Release 3.8.3
| Units &rarr; Advanced Options (Here be dragons!)
| Wind speed average decimals
| 1 (displayed as blank)
| Select a number of decimal places to overwrite the default. (NOTE: If the weather station does not provide an average wind speed, or if the user requires a change of units from how the weather station reports it, then CMX will calculate it to 1 decimal place by default; otherwise average wind speed will default to integer, or to one decimal place, depending how it is provided by the station).
| Select a number of decimal places to overwrite the default
|-
| WindSpeedDecimals=2
| Release 3.8.3
| Units &rarr; Advanced Options (Here be dragons!)
| Wind speed average decimals
| 2 (displayed as blank)
| Select a number of decimal places to overwrite the default which depends both on the weather station type and what units have been selected by user (speeds are normally reported as integers unless metres per second are reporting unit, because most sensors are not precise enough to give any decimal places in other units)
| Select a number of decimal places to overwrite the default
|-
| WindUnit=0
| (displayed as blank)
| Enter a 4 digit year:
* Legacy Releases (1.7.12 from 5 July 2008) and MX up to 3.11.4 (build 3133 from 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 thisthe current calendar year ifduring your first season starts(remember to change thisthe year, andmid-season setwhen thisreach to1 lastJanuary), and delete the year ifwhen your second season hasstarts started andas you don't want the previous value added to your second season
* From Release 3.12.0 (??29 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 startswould start had it been a full season (be that last calendar year or this calendar year)
|}
5,838

edits