Cumulus.ini (preserving history): Difference between revisions

m
→‎Read-Write parameters in the Station section: Mention MX as a service is only addition, no other change although minor clarity improvements
m (Text replacement - "[[MXDiags" to "[[MXDiags_folder")
m (→‎Read-Write parameters in the Station section: Mention MX as a service is only addition, no other change although minor clarity improvements)
Line 810: Line 810:


[[File:Badge vMx.png]] - Set as 'Stop 2nd instance' in Station Settings page. Not available in earliest builds of MX.
[[File:Badge vMx.png]] - Set as 'Stop 2nd instance' in Station Settings page. Not available in earliest builds of MX.
|-
|ConfirmClose=0
|{{Version badge 1}}Selected in the Station Configuration Screen Program Settings block. Toggles Confirmation you wish to close Cumulus application after telling it to close
*0 = Disabled, application will close immediately
*1 = Enabled, application will prompt for confirmation that you wish to close it (do not use this if you might suspend/standby/hibernate your computer)
[[File:Badge vMx.png]]Ignored by MX.
|-
|CloseOnSuspend=1
|{{Version badge 1}}If this is selected, in the Station Configuration Screen Program Settings block, Cumulus will close if you suspend/standby/hibernate your computer.  You should not select the previous parameter 'ConfirmClose' if you use this option.
*0 = Disabled, application will not close if you suspend/standby/hibernate your computer (it is highly recommended you close Cumulus manually before your computer is put into suspend/standby/hibernate state) 
*1 = Enabled, application will close on suspend/standby/hibernate of your computer (recommended if your computer can go into any of these states when left alone)
Ignored by MX
|-
|-
|DataLogInterval=2  
|DataLogInterval=2  
Line 927: Line 915:
|-
|-
|SpecialLog=0
|SpecialLog=0
|[[File:Badge vMx.png]] Not available in MX
|{{Version badge 1}}In Cumulus 1 there is an option of whether to record temperature and humidity (both indoor and outside values) in a log:
 
{{Version badge 1}}In Cumulus 1 there is an option of whether to record temperature and humidity (both indoor and outside values) in a log:
* 0 (default) = no special log
* 0 (default) = no special log
* 1 = Add this entry to start updating a file called 'speciallog.txt' in the data folder with the following fields:
* 1 = Add this entry to start updating a file called 'speciallog.txt' in the data folder with the following fields:
Line 936: Line 922:


See [https://cumulus.hosiene.co.uk/viewtopic.php?f=5&t=15040 forum]
See [https://cumulus.hosiene.co.uk/viewtopic.php?f=5&t=15040 forum]
[[File:Badge vMx.png]] '''SpecialLog''' parameter is ignored in MX
|-
|ConfirmClose=0
|{{Version badge 1}}Selected in the Station Configuration Screen Program Settings block. Toggles Confirmation you wish to close Cumulus application after telling it to close
*0 = Disabled, application will close immediately
*1 = Enabled, application will prompt for confirmation that you wish to close it (do not use this if you might suspend/standby/hibernate your computer)
[[File:Badge vMx.png]]'''ConfirmClose''' parameter is ignored by MX.
|-
|CloseOnSuspend=1
|{{Version badge 1}}If this is selected, in the Station Configuration Screen Program Settings block, Cumulus will close if you suspend/standby/hibernate your computer.  You should not select the previous parameter 'ConfirmClose' if you use this option.
*0 = Disabled, application will not close if you suspend/standby/hibernate your computer (it is highly recommended you close Cumulus manually before your computer is put into suspend/standby/hibernate state) 
*1 = Enabled, application will close on suspend/standby/hibernate of your computer (recommended if your computer can go into any of these states when left alone)
'''CloseOnSuspend=1''' ''is ignored by MX, however if you are running a MX release that permits running MX as a service, and'' '''you do run MX as a service''', ''the service handler on the Windows Operating System, does respond to suspend/standby/hibernate conditions.''
|-
|-
|colspan="2" style="background:lightblue;"| Cumulus MX only
|colspan="2" style="background:lightblue;"| Cumulus MX only
Line 942: Line 944:
|[[File:Badge vMx.png]] From version 3.5.1, Cumulus MX  will set new records (available in [[Webtags#Extreme_Records|Extreme Records Web Tags]]) from the time of the record until a timeout value (default 24 hours). You can change the default timeout by adding this parameter, and changing the default '24' to the number of hours that suit you.  
|[[File:Badge vMx.png]] From version 3.5.1, Cumulus MX  will set new records (available in [[Webtags#Extreme_Records|Extreme Records Web Tags]]) from the time of the record until a timeout value (default 24 hours). You can change the default timeout by adding this parameter, and changing the default '24' to the number of hours that suit you.  


This parameter is not available in any earlier versions (not in MX up to 3.5.0 nor any {{Version badge 1}} Cumulus 1 version).
This parameter is not available in any earlier versions (i.e. not in MX up to, and including, 3.5.0; nor in any {{Version badge 1}} Cumulus 1 version).
|-
|-
|Logging=0
|Logging=0
|This parameter can be edited in the file, or in station settings, or by use of a parameter when starting MX. It controls whether MX stores extra diagnostic information about its interaction with the weather station.
|This parameter can be edited in the file, or in station settings, or by use of a parameter when starting MX. It controls whether MX stores extra diagnostic information about its interaction with the weather station.
{{Version badge 1}} Cumulus 1 ignores this parameter, see [[Diagnostics]].
|-
|-
|RecordSetTimeoutHrs=24
|RecordSetTimeoutHrs=24
|[[File:Badge vMx.png]]Available in MX version 3.5.1 onwards only, allows the time from when a record is set to when it is cleared to be varied. The web tags: TempRecordSet, WindRecordSet, RainRecordSet, HumidityRecordSet, PressureRecordSet, HighTempRecordSet,LowTempRecordSet, HighAppTempRecordSet, LowAppTempRecordSet, HighHeatIndexRecordSet, LowWindChillRecordSet, HighMinTempRecordSet, LowMaxTempRecordSet, HighDewPointRecordSet, LowDewPointRecordSet, HighWindGustRecordSet, HighWindSpeedRecordSet, HighRainRateRecordSet,HighHourlyRainRecordSet, HighDailyRainRecordSet, HighMonthlyRainRecordSet, HighhHumidityRecordSet, HighWindrunRecordSet, LowHumidityRecordSet, HighPressureRecordSet, LowPressureRecordSet, LongestDryPeriodRecordSet, LongestWetPeriodRecordSet, HighTempRangeRecordSet, LowTempRangeRecordSet will all return 1 from when relevant record is set for the period of time set here (default 24 hours) and then reset to 0.
|[[File:Badge vMx.png]]Available in MX version 3.5.1 onwards only, allows the time from when a record is set to when it is cleared to be varied.  
 
The web tags: TempRecordSet, WindRecordSet, RainRecordSet, HumidityRecordSet, PressureRecordSet, HighTempRecordSet,LowTempRecordSet, HighAppTempRecordSet, LowAppTempRecordSet, HighHeatIndexRecordSet, LowWindChillRecordSet, HighMinTempRecordSet, LowMaxTempRecordSet, HighDewPointRecordSet, LowDewPointRecordSet, HighWindGustRecordSet, HighWindSpeedRecordSet, HighRainRateRecordSet,HighHourlyRainRecordSet, HighDailyRainRecordSet, HighMonthlyRainRecordSet, HighhHumidityRecordSet, HighWindrunRecordSet, LowHumidityRecordSet, HighPressureRecordSet, LowPressureRecordSet, LongestDryPeriodRecordSet, LongestWetPeriodRecordSet, HighTempRangeRecordSet, LowTempRangeRecordSet will all return 1 from when relevant record is set for the period of time set here (default 24 hours) and then reset to 0.
|}
|}


5,838

edits