5,838
edits
Cumulus.ini (preserving history): Difference between revisions
Cumulus.ini (preserving history) (view source)
Revision as of 19:18, 3 February 2021
, 19:18, 3 February 2021→Davis family specific:
m (→Read-Write parameters in the Station section: Mention MX as a service is only addition, no other change although minor clarity improvements) |
|||
| Line 1,053: | Line 1,053: | ||
|- | |- | ||
|RestartIfDataStops=0 | |RestartIfDataStops=0 | ||
| | |{{Version badge 1}}This read-only parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen. | ||
{{Version badge 1}}This read-only parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen. | |||
*0 (default) = Cumulus will just stop logging, and processing data, if it has had no data from the Davis station for 60 seconds. As it says in the Cumulus 1 help, use of this parameter may not fix a connection problem. With this default setting a connection problem stops Cumulus logging, so once you have fixed the problem it will download the missing data when you start it up again. | *0 (default) = Cumulus will just stop logging, and processing data, if it has had no data from the Davis station for 60 seconds. As it says in the Cumulus 1 help, use of this parameter may not fix a connection problem. With this default setting a connection problem stops Cumulus logging, so once you have fixed the problem it will download the missing data when you start it up again. | ||
*1 = Cumulus 1 attempts to restart itself if it has had no data from the station for 60 seconds. Davis stations can use this option explained in the [[#La_Crosse_specific:|La Crosse]] table if Cumulus sometimes fails to read information from the logger. Again, this may not fix the problem, but this setting does force Cumulus to have another attempt after making a new connection on start up. | *1 = Cumulus 1 attempts to restart itself if it has had no data from the station for 60 seconds. Davis stations can use this option explained in the [[#La_Crosse_specific:|La Crosse]] table if Cumulus sometimes fails to read information from the logger. Again, this may not fix the problem, but this setting does force Cumulus to have another attempt after making a new connection on start up. | ||
| Line 1,066: | Line 1,064: | ||
|- | |- | ||
|UseDavisLoop2=1 | |UseDavisLoop2=1 | ||
| | |[[File:Badge vMx.png]]This read-only parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen. | ||
[[File:Badge vMx.png]]This read-only parameter (attribute=value) is added directly to the file, it does not appear on a configuration screen. | |||
The current MX code uses ''LOOP2'' for two purposes. First, it uses the 'peak 10-minute gust' value, to avoid the problem where a gust might be missed, and secondly it uses the 'absolute pressure' value to make calculation of 'altimeter pressure' easier and more accurate. This is mainly used if you upload to CWOP. | The current MX code uses ''LOOP2'' for two purposes. First, it uses the 'peak 10-minute gust' value, to avoid the problem where a gust might be missed, and secondly it uses the 'absolute pressure' value to make calculation of 'altimeter pressure' easier and more accurate. This is mainly used if you upload to CWOP. | ||