Cumulus.ini (preserving history): Difference between revisions

Cumulus.ini (preserving history) (view source)

1,144 bytes added , 19:04, 10 January 2021

m

→‎Spike Removal: Clarify final parameter

5,838

edits

@@ Line 1,224: / Line 1,224: @@
 |This is set in the spike removal frame on the Calibration settings screen off the configuration menu. A humidity change 'spike removal' filter, ''changes in read value'' from any station greater than the value (as %) specified here (with a default of '''999.0''') will be ignored by Cumulus.
+|-
+|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}}
+*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]] Before version 3.7.0
+*Default is zero as shown, disabling the spike removal feature.
+*Add this line to file with Cumulus MX stopped, and set to 1 for the spike removal feature to be enabled.
+[[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.
 |}