Cumulus.ini (preserving history): Difference between revisions

Cumulus.ini (preserving history) (view source)

Revision as of 18:57, 10 January 2021

996 bytes removed , 18:57, 10 January 2021

m

→‎Read-only parameters in the Station section: standardising way options shown

Sfws

5,838

edits

@@ Line 564: / Line 564: @@
 |style="background:lightgray;"|[Station]
 |style="background:lightgray;"|Section name - the following parameters relate to all weather stations.
-|-
-|StartDate=13/08/2009
-|This parameter is different to all the others. It is not read-write as you cannot edit it in Cumulus (1 or MX). Unlike other read-only parameters it is automatically inserted into Cumulus.ini and given a value when Cumulus is first run. By default this will be set to the date of initial installation of the Cumulus application (whichever flavour).
-This date can be included in a template file, using the tag '''<#recordsbegandate>'''. The tag appears twice in the '''recordT.htm''' template that is provided with Cumulus (1 and MX) and there is a suggestion about changing that at [[FAQ#I_have_inserted_pre-Cumulus_data_making_.27Records_began_on.27_date_wrong]]
-|-
-|UseDataLogger=1
-|{{Version badge 1}}Cumulus 1.x.y: Selected in the [[Cumulus_Screenshots#Configuration_Menu_Screens|Station Configuration Screen]].
-[[File:Badge vMx.png]]Cumulus MX: This parameter (attribute=value) is added directly to the file in the [Station] section if you want to change the default, it does not appear on the settings screen.
-*0 = Disabled, at start-up, Cumulus will not download data from the station's data logger (if it has one) but just start with next observations.
-*1 = Enabled (Default), at start-up Cumulus will download data from the station's data logger (if it has one) to catch up from the point where Cumulus was last shut down. See last parameter for advice re station logging interval.
 |-
 |colspan="2" style="background:pink;"|Read-only parameters - The parameters listed below must be entered directly into file with Cumulus stopped. Used in both C1 and MX unless indicated.
@@ Line 614: / Line 601: @@
 |If the parameter is not included in the file, the default value is assumed.
-= turn off creation of '''wxnow.tx'''t file (stored in main Cumulus folder)
+*    0= turn off creation of '''wxnow.tx'''t file (stored in main Cumulus folder)
-= (default) create '''wxnow.txt''' file (an alternative way to get data to CWOP/APRS)
+*    1= (default) create '''wxnow.txt''' file (an alternative way to get data to CWOP/APRS)
 |-
 |ListWebTags=0
 |If the parameter is not included in the file, the default value is assumed.
-= (default) turn off creation of WebTags.txt file (stored in main Cumulus folder)
+*    0= (default) turn off creation of WebTags.txt file (stored in main Cumulus folder)
-= create WebTags.txt file when Cumulus is restarted (contains an unordered list of all the web tags your Cumulus build will recognise and process)
+*    1= create WebTags.txt file when Cumulus is restarted (contains an unordered list of all the web tags your Cumulus build will recognise and process)
 |-
 |RainDayThreshold=-1
@@ Line 677: / Line 664: @@
 |-
 |ErrorLogSpikeRemoval=0
-|This parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen on C1 or MX prior to v3.7.0. {{Version badge 1}}??C1 keeps the number of messages in the error log window to a maximum of 256?
+|This parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen on C1 or MX prior to v3.7.0.
-[[File:Badge vMx.png]] From version 3.7.0 the default for new installs is now 1. It can be set from the calibration settings screen. It controls the logging of both data spikes and data limits being exceeded. Recommended to be turned on.
+{{Version badge 1}}
+*Default is zero as shown, disabling the spike removal feature.
+*Add this line to file with Cumulus 1 stopped, and set to 1 for the spike removal feature to be enabled.
+??It appears that C1 limits the number of messages in the error log window to a maximum of 256, so that limit may affect reporting of spike removal, but hopefully it does not restrict the functionality of spike removal ?? '''Could someone verify that, and update this entry'''
+[[File:Badge vMx.png]] From version 3.7.0
+*the default for new installs is now 1.
+* change to zero if you don't want this feature. It can be set from the calibration settings screen. It controls the logging of both data spikes and data limits being exceeded. Recommended to be turned on.
 |}