FAQ: Difference between revisions

38 bytes added ,  19:36, 26 July 2020
m
Line 494: Line 494:
... check you have the correct station type selected (see the Cumulus ''Help'' for the settings screen).
... check you have the correct station type selected (see the Cumulus ''Help'' for the settings screen).


Choosing the wrong station type means individual items of information are not correctly assigned to weather parameters.  Cumulus knows what is at what location for each station type.  
{{Version badge 1}}Choosing the wrong station type means individual items of information are not correctly assigned to weather parameters.  Cumulus knows what is at what location for each station type.  
*Is the information ''correct on the station console'' (i.e. not a fault with a sensor), but incorrectly displayed on Cumulus screen (i.e. transfer problem)?  
*Is the information ''correct on the station console'' (i.e. not a fault with a sensor), but incorrectly displayed on Cumulus screen (i.e. transfer problem)?  
Check all your settings on Cumulus, or see a [[#Cumulus_can.27t_read_a_data_update_from_my_station|previous question]].
Check all your settings on Cumulus, or see a [[#Cumulus_can.27t_read_a_data_update_from_my_station|previous question]].
Line 509: Line 509:
The purpose of the backup files is to allow Cumulus to be 'rewound' to a particular point in time.  It simulates the situation where someone had closed Cumulus down at that point, and is only now starting it up again, and needs data to be downloaded from the station's logger to catch up to the present time. Obviously this cure will not work if your station type does not have a logger (one is needed for Cumulus to read old readings again).
The purpose of the backup files is to allow Cumulus to be 'rewound' to a particular point in time.  It simulates the situation where someone had closed Cumulus down at that point, and is only now starting it up again, and needs data to be downloaded from the station's logger to catch up to the present time. Obviously this cure will not work if your station type does not have a logger (one is needed for Cumulus to read old readings again).
*If you have only installed Cumulus a few days ago, or have just re-started Cumulus after it was stopped and encounter multiple ''rogue readings in the catch-up from the station logger''; '''one possibility''' is to stop Cumulus and find the [[#On_restarting_Cumulus.2C_it_did_not_successfully_read_all_data_from_when_it_last_ran|backup files]] that it took when you started it up (or just after the previous roll-over time), copy those files into the data folder, overwriting the ones that are there, then when you start it up again it will rewind back to the time in that back-up, and could sort itself out.
*If you have only installed Cumulus a few days ago, or have just re-started Cumulus after it was stopped and encounter multiple ''rogue readings in the catch-up from the station logger''; '''one possibility''' is to stop Cumulus and find the [[#On_restarting_Cumulus.2C_it_did_not_successfully_read_all_data_from_when_it_last_ran|backup files]] that it took when you started it up (or just after the previous roll-over time), copy those files into the data folder, overwriting the ones that are there, then when you start it up again it will rewind back to the time in that back-up, and could sort itself out.
The Cumulus 1 [[Diags|Diagnostic]] log often contains useful information for sorting out what has been read, which values have been ignored, and which highs or lows may have been updated incorrectly. Note that automatic backups are made just after roll-over time because restarting Cumulus when there are no logger records to read before roll-over has been known to cause problems. Therefore, the backup to choose might be one with the date before when the problem occurred, but remember that any calculations Cumulus makes are based on readings at least every minute when Cumulus is running, but for the catch up period such calculations can only use the readings available at your station's logging interval. Note if you choose a later backup and it does not work, you can always then repeat the 'rewind' with a earlier backup.
{{Version badge 1}}The Cumulus 1 [[Diags|Diagnostic]] log often contains useful information for sorting out what has been read, which values have been ignored, and which highs or lows may have been updated incorrectly. Note that automatic backups are made just after roll-over time because restarting Cumulus when there are no logger records to read before roll-over has been known to cause problems. Therefore, the backup to choose might be one with the date before when the problem occurred, but remember that any calculations Cumulus makes are based on readings at least every minute when Cumulus is running, but for the catch up period such calculations can only use the readings available at your station's logging interval. Note if you choose a later backup and it does not work, you can always then repeat the 'rewind' with a earlier backup.


== How to restore a corrupted log file ==
== How to restore a corrupted log file ==
5,838

edits