5,838
edits
FAQ: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→My temperature Min/Max/Avg graph is empty
m (corrected a link) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 273: | Line 273: | ||
* Each time Cumulus (both 1 and MX) reads records from the weather station it applies any change to the 'total rain count' against today's total in its memory. This "Count" approach has been chosen because different weather stations output different values, and an independent count is a way of working that can be applied for any weather station. | * Each time Cumulus (both 1 and MX) reads records from the weather station it applies any change to the 'total rain count' against today's total in its memory. This "Count" approach has been chosen because different weather stations output different values, and an independent count is a way of working that can be applied for any weather station. | ||
**As you will see if you look in [[ | **As you will see if you look in [[diags_folder]], Cumulus stores the 'total rain count' figure at rollover, so by maintaining the current figure it can subtract off the start of day figure to deduce the rainfall today and this is shown on the front screen in Cumulus 1, labelled ''Today''. In Cumulus 1 the '''Edit''' menu gives access to the ''Today's rain'' screen and that provides the ability to edit the start of day figure so that the figure shown for today is correct. Equivalent functionality is provided in Cumulus MX. If there is no rain in a day, the start of day count will be the same at the start of the next day. | ||
**Today's rain is added to the figures (as described above) derived from dayfile.txt for what the front screen in Cumulus 1, labels '''This month''', and ''This year'' (this last figure is the seasonal total, you can choose for it to start on 1 January or any other month). Thus these figures are updated each time Cumulus receives a rain reading from the station (they all include today-so-far), and these figures will not be displayed if Cumulus is unable to read rain information from your station. | **Today's rain is added to the figures (as described above) derived from dayfile.txt for what the front screen in Cumulus 1, labels '''This month''', and ''This year'' (this last figure is the seasonal total, you can choose for it to start on 1 January or any other month). Thus these figures are updated each time Cumulus receives a rain reading from the station (they all include today-so-far), and these figures will not be displayed if Cumulus is unable to read rain information from your station. | ||
** The today's total so far at each reading time is also added to the 'recent tag' array allowing total values for the day-so-far at one minute intervals for up to a week ago to be added as web tags to a web template. | ** The today's total so far at each reading time is also added to the 'recent tag' array allowing total values for the day-so-far at one minute intervals for up to a week ago to be added as web tags to a web template. | ||
| Line 510: | Line 510: | ||
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. | ||
{{Version badge 1}}The Cumulus 1 [[ | {{Version badge 1}}The Cumulus 1 [[Diags_folder|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 == | ||
| Line 739: | Line 739: | ||
== When I start Cumulus, the graphs restart again each time and don't show the earlier data == | == When I start Cumulus, the graphs restart again each time and don't show the earlier data == | ||
{{Version badge 1}}You probably have an error in one or more data files. Look near the beginning of the latest file in the | {{Version badge 1}}You probably have an error in one or more data files. Look near the beginning of the latest file in the [[Diags_folder|sub-folder called 'diags']] for an error message which will tell you which file is in error and which line is causing the problem. It may simply be a blank line. Edit the file with Cumulus stopped. Note that you may need to repeat this process; only the first error is shown. | ||
This problem can also occur if you change your system format settings (date format, decimal and list separators etc). Again, check the diags file for a message about a number not being a valid floating point value. | This problem can also occur if you change your system format settings (date format, decimal and list separators etc). Again, check the diags file for a message about a number not being a valid floating point value. | ||
| Line 816: | Line 816: | ||
The most likely explanation is that you have only recently started running Cumulus (in the last day or two). It adds new values to this graph at the end of each day; it wouldn't make sense to add a value part of the way through the day, and you need a few points to be plotted before the graph starts to take shape. You need to wait until you have been running Cumulus for a few days. | The most likely explanation is that you have only recently started running Cumulus (in the last day or two). It adds new values to this graph at the end of each day; it wouldn't make sense to add a value part of the way through the day, and you need a few points to be plotted before the graph starts to take shape. You need to wait until you have been running Cumulus for a few days. | ||
If you've been running Cumulus for more than a few days, but the graph is still empty, the most likely explanation is that it was unable to read your dayfile.txt file. Look at the latest file in the 'diags' folder (the files are plain text) for error messages mentioning dayfile.txt. | If you've been running Cumulus for more than a few days, but the graph is still empty, the most likely explanation is that it was unable to read your dayfile.txt file. Look at the latest file in the [[Diags_folder|'diags']] folder (the files are plain text) for error messages mentioning dayfile.txt. | ||
== The longest dry/wet spell for this month/year includes days from last month/year == | == The longest dry/wet spell for this month/year includes days from last month/year == | ||
| Line 896: | Line 896: | ||
If you look in the status bar at the bottom of the Cumulus window, there may a message "Error: no response"; this would confirm that the station has locked up and needs resetting. | If you look in the status bar at the bottom of the Cumulus window, there may a message "Error: no response"; this would confirm that the station has locked up and needs resetting. | ||
If you are using the "Synchronise" setting but are still getting frequent console interface lockups, then the clocks on the console and the platform running Cumulus may be drifting too far between synchronisations. Look in the | If you are using the "Synchronise" setting but are still getting frequent console interface lockups, then the clocks on the console and the platform running Cumulus may be drifting too far between synchronisations. Look in the [[diags_folder]] files for the word "drift" and see how many seconds apart the clocks are drifting. If it is more than 3 seconds, you will need to adjust the period that Cumulus allows where it doesn't read the console data. Stop Cumulus and edit Cumulus.ini. In the [Station] section, add a line: | ||
FOReadAvoidPeriod=N | FOReadAvoidPeriod=N | ||
| Line 1,163: | Line 1,163: | ||
**Deselect the option where indicated by red arrow if your template includes something like <code><meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" /></code> | **Deselect the option where indicated by red arrow if your template includes something like <code><meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" /></code> | ||
**For customised pages, (without standard Cumulus template names), select/un-select the UTF-8 encoding in the appropriate column on the '''Configuration''' menu, ''Internet'' dialog, '''Files''' tab screen where you list the local and remote names. | **For customised pages, (without standard Cumulus template names), select/un-select the UTF-8 encoding in the appropriate column on the '''Configuration''' menu, ''Internet'' dialog, '''Files''' tab screen where you list the local and remote names. | ||
*Or you have edited/customised the template and added an incorrectly specified Cumulus [[webtags]] that has caused [[Customised_templates#What_is_meant_by_.27Cumulus_processes_templates.27| Cumulus processing]] to abort for that template. If you stop cumulus you can use a text editor to open the latest [[ | *Or you have edited/customised the template and added an incorrectly specified Cumulus [[webtags]] that has caused [[Customised_templates#What_is_meant_by_.27Cumulus_processes_templates.27| Cumulus processing]] to abort for that template. If you stop cumulus you can use a text editor to open the latest [[Diags_folder|diagnostic file]]. Look at entries time-stamped just before the hour and repeated at your auto-update ''interval'' (just below red arrow in screen image above). You might find a message like "Error processing C:\web\indexT" (i.e. mentioning whichever template is at fault) followed by a brief hint as to the nature of the error. | ||
== My web pages have obsolete web tag values in them == | == My web pages have obsolete web tag values in them == | ||
