Cumulus.ini (preserving history): Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
m (→‎Section: FTP site: add note that this section needs updating)
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="background: LemonChiffon;padding:5px; margin:2px;">
[[File:Crystal Clear info.png|40px]] This page was last updated for the MX release in July 2020; that is no longer latest!
Appeal to contributors: Please work through all MX release announcements and work out all the many updates needed for this page, it may even need a redesign for more recent releases!
</div>
[[File:Badge vMx.png]] This page now only applies if you are using Cumulus MX.
[[File:Badge vMx.png]] This page now only applies if you are using Cumulus MX.


If you are using Cumulus 1, all the information is now on [[Cumulus.ini (Cumulus 1)]] page.
The information for the legacy Cumulus has been moved to the new [[Cumulus.ini (Cumulus 1)]] page.


[[Category: Configuration_Files]]
[[Category: Configuration_Files]]
Line 449: Line 456:
=== Spike Removal ===
=== Spike Removal ===


Which parameters are available from this section depends on release of MX being used, and which type of staion you use.
Which parameters are available from this section depends on release of MX being used, and which type of station you use.




Line 966: Line 973:
*2 Minimum value
*2 Minimum value
*3 = default value
*3 = default value
Sets the interval (in seconds) during each 48 (or 60 for some models in Cumulus 1) second of station logging period when Cumulus will avoid reading the station data to try and minimise lock ups. If the clock drifts more than this value in 24 hours, then Cumulus may cause the station to lock up when reading the data. The actual station clock drift gets logged to the diags file when the re-synchronise (see last parameter) takes place, this will give an idea of whether it would be useful to adjust this setting.
Sets the interval (in seconds) when Cumulus will avoid reading the station data to try and minimise lock ups. If the clock drifts more than this value in 24 hours, then Cumulus may cause the station to lock up when reading the data. The actual station clock drift gets logged to the diags file when the re-synchronise (see last parameter) takes place, this will give an idea of whether it would be useful to adjust this setting.
 
Note: I have not been able to find any interval that works. In my experience, if you use this setting, MX skips every attempt to read from the weather station, As MX is coded to make an attempt every 60 seconds, but is also coded to skip every 60 seconds plus or minus the setting here.


MX applies both 48 and 60 second avoidances regardless of model.
MX applies both 48 and 60 second avoidances regardless of model.
Line 1,277: Line 1,286:
|?
|?
|-
|-
|colspan="2" style="background:pink;"|The following parameters are those available at release 3.6.0 (unless marked otherwise)
|colspan="2" style="background:pink;"|The following parameters are those available at release 3.6.0 (where a parameter is not available at all earlier releases, the first version using it is shown)
|-
|-
|DailyProgram=  
|DailyProgram=  
5,838

edits

Navigation menu