FAQ: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search

FAQ (view source)

Revision as of 16:35, 22 March 2021

871 bytes removed ,  16:35, 22 March 2021
m
Text replacement - "Cumulus.ini" to "Cumulus.ini_(Cumulus_1)"
m (Text replacement - "Cumulus.ini" to "Cumulus.ini_(Cumulus_1)")
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is the <big>Cumulus 1 FAQ</big> (consult also the Help screens within Cumulus software, and learn more from the rest of this Wiki)
This is the
 
<big>Cumulus 1 FAQ</big>
 
(consult also the Help screens within Cumulus software, and learn more from the rest of this Wiki)


Some references to other flavours of Cumulus are included here. There is also a separate FAQ specifically for [[Cumulus MX FAQ|Cumulus MX]].
Some references to other flavours of Cumulus are included here. There is also a separate FAQ specifically for [[Cumulus MX FAQ|Cumulus MX]].
Line 6: Line 10:




== Should I use Cumulus 1 or Cumulus 2 or Cumulus 3 (MX)? ==
Steve Loft (who originated all 3 versions) had no recommendations one way or the other. However, since he focussed on enjoying retirement and withdrew from involvement in Cumulus, a lot has changed.
Now newcomers should probably choose Cumulus MX, but read on if you are not sure.


Cumulus 1 is a finished version, and because the development environment is obsolete no further changes are possible. That said there have been two recent patches to the screen interface, allowing dates from 2021 to 2030 to be selected in drop downs, but the core code will never change. Cumulus 1 is reliable and has more functionality to cope with problems if your weather station set-up may experience problems. However, it does not support some new weather station models, and it will only run  on a Microsoft Windows device, so those two facts may imply you cannot use it! Although there remains some expertise with Cumulus 1 established users, any newcomer may prefer to choose a MX as that has more technical support available.
== What operating systems does Cumulus run on? ==


Cumulus 2 explored an improved data approach using UTC and having better handling of rainfall. Although it was hoped it would make enhancement easier, and allow use of alternative languages possible, it proved too complicated. and has been abandoned and is no longer available, so if you don't already have it hard luck. Subsequently, some of the developments in Cumulus 2 were ported into new version 1.9.0, and remain in final Cumulus 1.9.4 from where they were in turn ported to Cumulus MX. So whichever of the two versions still available you choose, you are benefiting from work done for Cumulus 2.
Cumulus 1 - All versions of Windows from XP to Windows 10 inclusive (and the server versions). It works on 32 bit and 64 bit editions. It may also work on Windows 2000, but this is not supported. You will probably not be able to get it to work on Windows 2000 with a Fine Offset station.


Cumulus 3 is live and is still being improved. It is more often known as [[Cumulus MX]]. It is using a different architecture (partly inspired by Cumulus 2), it provides some enhancements in functionality and will run on a range of platforms. It can be used in a production system as it has good reliability,  but perhaps should be avoided in a few rare cases where people's systems are not very reliable. Initially MX lacked several key parts of the functionality in Cumulus 1, but the number of such facilities continues to decrease as Mark Crossley is adding missing functionality.


== What operating systems does Cumulus run on?  ==


Cumulus 1 - All versions of Windows from XP to Windows 10 inclusive (and the server versions). It works on 32 bit and 64 bit editions. It may also work on Windows 2000, but this is not supported. You will probably not be able to get it to work on Windows 2000 with a Fine Offset station.
== Where do I find the Cumulus 1 installer? ==


Cumulus MX runs on Windows from Windows 7 onwards, and on Linux and Mac OS X.
All available via the [[Downloads|Downloads page]] in this Wiki


== Where do I find the Cumulus installer? ==
== What do I need to get right when first getting Cumulus 1? ==


All available via the [[Software|Software page]] in this Wiki
== What do I need to get right when first getting Cumulus? ==
The installation process for Cumulus 1 displays '''readme.txt''', that has many tips. See also [[Setup]]. Below are three key points.
The installation process for Cumulus 1 displays '''readme.txt''', that has many tips. See also [[Setup]]. Below are three key points.
# Install Cumulus in its own directory directly under a drive root.
# Install Cumulus in its own directory directly under a drive root.
# Connect your weather station before you start Cumulus
# Connect your weather station before you start Cumulus
# When you first run Cumulus, it displays the '''Station settings''' screen. On this, make sure you pick the right sort of station (to ensure Cumulus communicates correctly with your weather station, and can identify all the observations) and choose your '''units''' wisely. (Changing units later means all stored Lowest and highest numbers up to that point have to be converted immediately manually).  See the '''Help''' for information about the rest of the screen, but generally you can easily adjust the other options later.
# When you first run Cumulus 1, it displays the '''Station settings''' screen. On this, make sure you pick the right sort of station (to ensure Cumulus communicates correctly with your weather station, and can identify all the observations) and choose your '''units''' wisely. (Changing units later means all stored Lowest and highest numbers up to that point have to be converted immediately manually).  See the '''Help''' for information about the rest of the screen, but generally you can easily adjust the other options later.


Cumulus MX is different, simply copy the whole download into its own directory (Cumulus MX is the preferred name), and connect your weather station before you run the engine via the executable "CumulusMX.exe". The user interface is separate, so you will need to connect to that interface in order to access the settings.


== What weather stations does Cumulus work with?  ==
 
== What weather stations does Cumulus 1 work with?  ==


{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
Line 67: Line 63:
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1


As of 2017, development of both Cumulus 1 and Cumulus MX was abandoned by Steve Loft. Although there have been a couple of patches to change the years listed in drop downs with Cumulus 1, its code is frozen as the relevant development environment is no longer available.  
As of 2017, development of Cumulus 1 was stopped by Steve Loft and a new version called Cumulus MX replaced it. Although there have been a couple of patches to change the years listed in drop downs with Cumulus 1, its code is frozen as the relevant development environment is no longer available.  


Consequently, there is no possibility of any new features for Cumulus 1.
Consequently, there is no possibility of any new features for Cumulus 1.
Line 137: Line 133:
*It can be useful to take copies of the Cumulus 'backup' sub-folder on key dates (e.g. at change of month or year), or if you think you might have some rogue figures.  The '.ini' files in the backup sub-folder contain past extreme values that you might want to look up.
*It can be useful to take copies of the Cumulus 'backup' sub-folder on key dates (e.g. at change of month or year), or if you think you might have some rogue figures.  The '.ini' files in the backup sub-folder contain past extreme values that you might want to look up.
*You should also back up, at least once, your cumulus.ini file in the main Cumulus folder.  This contains all the key settings and you need a record of those!
*You should also back up, at least once, your cumulus.ini file in the main Cumulus folder.  This contains all the key settings and you need a record of those!
Recent builds of Cumulus MX back up the main log files and the Cumulus.ini file every time MX is restarted and every time it does a rollover to a new day. MX also has functionality to copy your observations and the derived values to a database so that provides another way of preserving your data.


== Moving Cumulus software to a different location on your PC? ==
 
== Moving Cumulus 1 software to a different location on your PC? ==


{{Version badge 1}}This article in the wiki gives more details above moving Cumulus: [[Moving cumulus]]
{{Version badge 1}}This article in the wiki gives more details above moving Cumulus: [[Moving cumulus]]
Line 153: Line 149:
The '''Configuration''' menu, ''Station'' setting screen (near bottom) has option to enter there the ''rainfall total'' for the bit of the year (starting month can be selected here too) until when you first start using Cumulus.  See the Cumulus '''Help''' for this screen for further details.
The '''Configuration''' menu, ''Station'' setting screen (near bottom) has option to enter there the ''rainfall total'' for the bit of the year (starting month can be selected here too) until when you first start using Cumulus.  See the Cumulus '''Help''' for this screen for further details.


Yes is the answer for other weather information, providing you can manipulate the information you have into either (preferably) the format used by the [[Monthly_log_files#Importing_pre-Cumulus_data]] or (second best) [[Dayfile.txt]]. Look up those cross-references in this Wiki (or the Cumulus '''Help''') for further information on required formats.  The support forum includes a few threads related to this topic, and if you post there then people who have already imported from particular systems may offer their services to import your past observations.
Yes is the answer for other weather information, providing you can manipulate the information you have into either (preferably) the format used by the [[Standard_log_files#Importing_pre-Cumulus_data]] or (second best) [[Dayfile.txt]]. Look up those cross-references in this Wiki (or the Cumulus '''Help''') for further information on required formats.  The support forum includes a few threads related to this topic, and if you post there then people who have already imported from particular systems may offer their services to import your past observations.


A converter for Weather Display log files is available from [[Software#Weather_Display_Converter|software page]]
A converter for Weather Display log files is available from [[Software#Weather_Display_Converter|software page]]
Line 160: Line 156:


== I was away on the last day of last month/year - How do I see the final lowest and highest figures for last month/year? ==
== I was away on the last day of last month/year - How do I see the final lowest and highest figures for last month/year? ==
{{Version badge 1}}
{{Version badge 1}}
'''View''' menu, ''This month'' or ''This year'' screens show some figures for any month or year selected by you, but do not show all the figures shown on a standard web page or as shown on the ''Highs and Lows'' screen for the current month/year.
'''View''' menu, ''This month'' or ''This year'' screens show some figures for any month or year selected by you, but do not show all the figures shown on a standard web page or as shown on the ''Highs and Lows'' screen for the current month/year.
Line 166: Line 163:
*Look in the ''backup\daily'' subfolder within your Cumulus installation.  
*Look in the ''backup\daily'' subfolder within your Cumulus installation.  
*These daily backups will be created if Cumulus was left running during the period of interest, or stopped before that period and since restarted.  
*These daily backups will be created if Cumulus was left running during the period of interest, or stopped before that period and since restarted.  
*Normally about 10 such back ups are available, each folder has a name based on the timestamp and contains the 6 [[:Category:Log_Files|xxxx.ini files]], the current [[Monthly_log_files|monthly standard data log]]/[[Extra_Sensor_Files|monthly extra data log]], and the most recent update of [[dayfile.txt|daily summary log]].
*Normally about 10 such back ups are available, each folder has a name based on the timestamp and contains the 6 [[:Category:Log_Files|xxxx.ini files]], the current [[Standard_log_files|monthly standard data log]]/[[Extra_Sensor_Files|monthly extra data log]], and the most recent update of [[dayfile.txt|daily summary log]].


Open as a text file [[month.ini]] in the folder whose name is bearing the timestamp after your final rollover, for Cumulus builds 1041 to 1088 the final lowest and highest for each observation in the month will be listed.
Open as a text file [[month.ini]] in the folder whose name is bearing the timestamp after your final rollover, for Cumulus builds 1041 to 1088 the final lowest and highest for each observation in the month will be listed.
Line 172: Line 169:
In a similar manner if you miss the last day of the year, for Cumulus builds 1041 to 1088 see the final 'this year' figures for last year by opening [[year.ini]] from the appropriate backup.
In a similar manner if you miss the last day of the year, for Cumulus builds 1041 to 1088 see the final 'this year' figures for last year by opening [[year.ini]] from the appropriate backup.


== What do the various wind speeds in Cumulus correspond to, with Davis stations?  ==
== What do the various wind speeds in Cumulus 1 correspond to, with Davis stations?  ==


Davis station firmware supplies two windspeeds, a 3-second average and a 10-minute average (later versions of the firmware also supply a 2-minute average, Cumulus currently doesn't use this).   
Davis station firmware supplies two wind speeds, a 3-second average and a 10-minute average (later versions of the firmware also supply a 2-minute average, Cumulus currently doesn't use this).   
* The latest Davis 3-second average is treated by Cumulus as 'Latest' (available via <#wlatest>, matching direction is '<#currentwdir>' and '<#bearing>')
* The latest Davis 3-second average is treated by Cumulus as 'Latest' (available via <#wlatest>, matching direction is '<#currentwdir>' and '<#bearing>')
* The highest of the station's 3-second readings over the previous 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.ini#Section:_Station]] where 'N' is number of) minutes becomes the Cumulus 'Gust (available via <#wgust>, no matching direction web tag). Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (so Cumulus reports this within an extended 10, or as configured, minute period, not the 'latest' gust).
* The highest of the station's 3-second readings over the previous 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.ini_(Cumulus_1)#Section:_Station]] where 'N' is number of) minutes becomes the Cumulus 'Gust (available via <#wgust>, no matching direction web tag). Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (so Cumulus reports this within an extended 10, or as configured, minute period, not the 'latest' gust).
* The Davis 10-minute average is the Cumulus 'Average' (available via <#wspeed>,  matching direction reported as '<#wdir>' and '<#avgbearing>').
* The Davis 10-minute average is the Cumulus 'Average' (available via <#wspeed>,  matching direction reported as '<#wdir>' and '<#avgbearing>').


Line 184: Line 181:
If the Cumulus figure seems lower than the Davis figure see [[#My_Davis_station_shows_a_higher_maximum_wind_speed_than_Cumulus]].
If the Cumulus figure seems lower than the Davis figure see [[#My_Davis_station_shows_a_higher_maximum_wind_speed_than_Cumulus]].


== What do the various wind speeds in Cumulus correspond to, with Fine Offset stations?  ==
== What do the various wind speeds in Cumulus 1 correspond to, with Fine Offset stations?  ==


Fine Offset sensors measure wind over 48-second intervals, divided into 24 2-second intervals. At the end of each 48-second period,  the outdoor unit (anemometer) transmits two values, the "Gust" is calculated from the number of revolutions of the anemometer in last two seconds and the "Average" from the number of revolutions adding all two second counts in the 48 seconds. The console keeps '''overwriting''' the newly received 'Gust' and 'Wind' values to the same area of console memory every 48 seconds, until the station logging interval time is reached, then it moves on to the next memory location, leaving the last values it wrote in the previous console memory location.  
Fine Offset sensors measure wind over 48-second intervals, divided into 24 2-second intervals. At the end of each 48-second period,  the outdoor unit (anemometer) transmits two values, the "Gust" is calculated from the number of revolutions of the anemometer in last two seconds and the "Average" from the number of revolutions adding all two second counts in the 48 seconds. The console keeps '''overwriting''' the newly received 'Gust' and 'Wind' values to the same area of console memory every 48 seconds, until the station logging interval time is reached, then it moves on to the next memory location, leaving the last values it wrote in the previous console memory location.  
Line 197: Line 194:


=== Summary with default selections ===
=== Summary with default selections ===
# '<#wgust>' contains "Calculated Wind Gust (highest value for any 2 seconds in last 10 minutes) Speed" reports highest console gust value in last 10 minutes (this is capturing WMO gust definition over a longer 10 minute reporting interval)
# '<#wgust>' contains "Calculated Wind Gust (highest value for any 2 seconds in last 10 minutes) Speed" reports highest console gust value in last 10 minutes (this is capturing WMO gust definition over a longer 10 minute reporting interval)
# '<#wlatest>' contains "Latest Peak (the value for last 2 seconds in 48 seconds prior to storing) Wind Speed" taken from console gust value (this is capturing the latest WMO Gust)
# '<#wlatest>' contains "Latest Peak (the value for last 2 seconds in 48 seconds prior to storing) Wind Speed" taken from console gust value (this is capturing the latest WMO Gust)
Line 202: Line 200:


=== In detail with all the configurations ===
=== In detail with all the configurations ===
* The highest of the Fine Offset 'Gust' values over the previous 10 (number fixed and not configured to match any other interval set) minutes becomes what Cumulus reports as the 'Gust' speed ('<#wgust>').  Cumulus does not report a matching direction for this as a web tag, although it will be somewhere in array '<#wdirdata>'.
* The highest of the Fine Offset 'Gust' values over the previous 10 (number fixed and not configured to match any other interval set) minutes becomes what Cumulus reports as the 'Gust' speed ('<#wgust>').  Cumulus does not report a matching direction for this as a web tag, although it will be somewhere in array '<#wdirdata>'.
* The value labelled 'Latest'('<#wlatest>', matching direction is '<#currentwdir>' and '<#bearing>') by Cumulus is Fine Offset console 'Gust' value. (Cumulus also adds each new latest value to the array <#wspddata> and moves the index of the array <#nextwindindex> onto the next position in the circular array.
* The value labelled 'Latest'('<#wlatest>', matching direction is '<#currentwdir>' and '<#bearing>') by Cumulus is Fine Offset console 'Gust' value. (Cumulus also adds each new latest value to the array <#wspddata> and moves the index of the array <#nextwindindex> onto the next position in the circular array.
Line 209: Line 208:
** If 'Calculate 10-min wind average' and 'Use speed for avg calculation' are both selected; the average of the Fine Offset 'Wind' values read over the previous N (configurable, defaults to 10) minutes is reported.
** If 'Calculate 10-min wind average' and 'Use speed for avg calculation' are both selected; the average of the Fine Offset 'Wind' values read over the previous N (configurable, defaults to 10) minutes is reported.


Select value for 'N' using ''AvgSpeedMinutes=N'' in [[Cumulus.ini#Section:_Station]].
Select value for 'N' using ''AvgSpeedMinutes=N'' in [[Cumulus.ini_(Cumulus_1)#Section:_Station]].


== How do I set up recording wind speeds in Cumulus, with Oregon Scientific and La Crosse stations  ==
== How do I set up recording wind speeds in Cumulus 1, with Oregon Scientific and La Crosse stations  ==


La Crosse and some Oregon Scientific weather stations only output a single wind speed.  To allow Cumulus to calculate 'gust' and 'wind speed' with different values, select the '''Station''' dialogue from the ''Configuration'' menu and set ''Calculate 10 min wind average'' in the 'Settings' frame, so in [[cumulus.ini]] this will produce the parameter 'Wind10MinAverage=1 when cumulus is next stopped.
La Crosse and some Oregon Scientific weather stations only output a single wind speed.  To allow Cumulus to calculate 'gust' and 'wind speed' with different values, select the '''Station''' dialogue from the ''Configuration'' menu and set ''Calculate 10 min wind average'' in the 'Settings' frame, so in [[cumulus.ini]] this will produce the parameter 'Wind10MinAverage=1 when cumulus is next stopped.
* The station's 'Wind' value will then display as Cumulus 'Latest'.
* The station's 'Wind' value will then display as Cumulus 'Latest'.
* A 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.ini#Section:_Station]] where 'N' is number of) minutes average of the station's 'Wind' value will then display as Cumulus 'Average'.
* A 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.ini_(Cumulus_1)#Section:_Station]] where 'N' is number of) minutes average of the station's 'Wind' value will then display as Cumulus 'Average'.
* The highest of the station's 'Wind' value in a 10 minute period will then display as Cumulus 'Gust'.  Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (not the maximum instantaneous wind speed).
* The highest of the station's 'Wind' value in a 10 minute period will then display as Cumulus 'Gust'.  Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (not the maximum instantaneous wind speed).


See ''LCMaxWind=X'' parameter in [[Cumulus.ini#La_Crosse_specific:]] where X is the maximum (uncalibrated) wind speed in m/s that you want to allow.
See ''LCMaxWind=X'' parameter in [[Cumulus.ini_(Cumulus_1)#La_Crosse_specific:]] where X is the maximum (uncalibrated) wind speed in m/s that you want to allow.


== How do I make Cumulus run automatically when Windows starts?  ==
== How do I make Cumulus 1 run automatically when Windows starts?  ==


{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
Line 227: Line 226:


== How does Cumulus handle Daylight Saving Time?  ==
== How does Cumulus handle Daylight Saving Time?  ==
Cumulus provides the option for you to use rollover at 9am winter time that is preserved throughout the year so all days are 24 hours long even when clock changes, simply click "Use 10am in summer" on the Station settings.
Cumulus provides the option for you to use rollover at 9am winter time that is preserved throughout the year so all days are 24 hours long even when clock changes, simply click "Use 10am in summer" on the Station settings.


Line 253: Line 253:
*See Fine Offset forum discussions for further information.
*See Fine Offset forum discussions for further information.


== What formula does Cumulus use for values derived from temperature?  ==
== What formula does Cumulus 1 use for values derived from temperature?  ==


[[Temperature_(and_humidity)_measurement#Cumulus_Calculated_Parameters|see Cumulus_Calculated_Parameters]]
[[Temperature_(and_humidity)_measurement#Cumulus_Calculated_Parameters|see Cumulus_Calculated_Parameters]]
Line 265: Line 265:
For stations which supply a rain rate, Cumulus uses that. For stations which don't supply a rain rate (e.g. Fine Offset and La Crosse), Cumulus simply takes the rain total from the last five minutes and calculates a rate based on that; e.g. a single tip of 0.3mm in 5 minutes is a rate of 3.6mm/hr. When data from the station's logger is used, a similar calculation is performed, but the interval used is the logger interval rather than five minutes.
For stations which supply a rain rate, Cumulus uses that. For stations which don't supply a rain rate (e.g. Fine Offset and La Crosse), Cumulus simply takes the rain total from the last five minutes and calculates a rate based on that; e.g. a single tip of 0.3mm in 5 minutes is a rate of 3.6mm/hr. When data from the station's logger is used, a similar calculation is performed, but the interval used is the logger interval rather than five minutes.


== Where does Cumulus get its this month and this year rainfall totals from?  ==
== Where does Cumulus 1 get its this month and this year rainfall totals from?  ==


* The rainfall totals (for this month, year, and season), are initialised when Cumulus is (re-)started by adding up the corresponding daily totals in [[dayfile.txt]] and storing those sums in memory.
* The rainfall totals (for this month, year, and season), are initialised when Cumulus is (re-)started by adding up the corresponding daily totals in [[dayfile.txt]] and storing those sums in memory.
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 [[diags]], 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.
**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.


* For the web tags, Cumulus (both 1 and MX) takes its stored sums and adds today's latest total each time, to give the current totals for this month and this rain season (year so far) when processing 'indexT.htm' web template which is where these figures ase shown (not on this month nor on this year templates).
* For the web tags, Cumulus (both 1 and MX) takes its stored sums and adds today's latest total each time, to give the current totals for this month and this rain season (year so far) when processing 'indexT.htm' web template which is where these figures ase shown (not on this month nor on this year templates).
**Important, for the <#ryear> web tag, and for the 'This year' display on the ''main'' Cumulus screen, the processing reads the ''dayfile.txt'' for the rainfall season starting with the month set on the station settings screen and stored as the value for attribute ''RainSeasonStart'' in [[Cumulus.ini#Section:_Station]] (its default is January).   
**Important, for the <#ryear> web tag, and for the 'This year' display on the ''main'' Cumulus screen, the processing reads the ''dayfile.txt'' for the rainfall season starting with the month set on the station settings screen and stored as the value for attribute ''RainSeasonStart'' in [[Cumulus.ini_(Cumulus_1)#Section:_Station]] (its default is January).   
**If you have set a 'year to date' value and Cumulus is being re-started when the year specified beside that figure matches the current calendar year, your year-to-date amount is also added into this year's total. This should normally only be relevant in your first rain season of operating Cumulus, but could be used if in any season you needed to add an extra amount because for some reason you had a gap in your recording period.  ''Do be aware that if you select a rain season starting in a month other than January, the year to date figure will stop being added on 1 January because the year specified next to the figure to add on will then be the previous calendar year!''
**If you have set a 'year to date' value and Cumulus is being re-started when the year specified beside that figure matches the current calendar year, your year-to-date amount is also added into this year's total. This should normally only be relevant in your first rain season of operating Cumulus, but could be used if in any season you needed to add an extra amount because for some reason you had a gap in your recording period.  ''Do be aware that if you select a rain season starting in a month other than January, the year to date figure will stop being added on 1 January because the year specified next to the figure to add on will then be the previous calendar year!''
**There is no corresponding setting for amending the total for the first 'this month' of Cumulus operation.  The only way round this is to manually change the rainfall in dayfile.txt for the first day of operation to include rainfall on all previous days of month, but that could potentially cause you to set the maximum daily rainfall extreme record wrongly.
**There is no corresponding setting for amending the total for the first 'this month' of Cumulus operation.  The only way round this is to manually change the rainfall in dayfile.txt for the first day of operation to include rainfall on all previous days of month, but that could potentially cause you to set the maximum daily rainfall extreme record wrongly.
Line 287: Line 287:
== How do I reset all my data to start again from scratch?  ==
== How do I reset all my data to start again from scratch?  ==


Stop Cumulus and delete all of the files in the data folder. You may also want to edit the 'StartDate=' line in [[cumulus.ini]] to set the date for the start of your data, if you are starting again on a different date.
Stop Cumulus 1 and delete all of the files in the data folder. You may also want to edit the 'StartDate=' line in [[cumulus.ini]] to set the date for the start of your data, if you are starting again on a different date, although Cumulus 1 does not make any decisions based on that date, it simply outputs it twice (!) on one standard web page.


== How do I localise Cumulus to my own language? ==
== How do I localise Cumulus 1 to my own language? ==


Cumulus does not directly support languages other than English. It was never intended for use in other languages, and it is not possible to add support for this now. However, the text used for:
Cumulus does not directly support languages other than English. It was never intended for use in other languages, and it is not possible to add support for this now. However, the text used for:
*Forecasting
*Forecasting
*Moonphases
*Moon phases
*Beaufort Scale
*Beaufort Scale
*Trend descriptions
*Trend descriptions
Line 299: Line 299:
*Graph titles
*Graph titles
*Extra sensor channels
*Extra sensor channels
can all be customised by using the [[strings.ini]] file. This facility may be extended to allow other items to be translated, but it is very unlikely that there will ever be a fully multi-language version of Cumulus in its current form.
can all be customised by using the [[strings.ini]] file.  


'''This wiki page [[:Category:Other_Languages|Other Languages]] has some obsolete (valid in 2009-2010) information about customising what were the standard web pages in versions of Cumulus 1 up to 1.8.x. The translations there are NOT compatible with later (or final) Cumulus 1 version, nor will they work with Cumulus MX.'''
'''This wiki page [[:Category:Other_Languages|Other Languages]] has some obsolete (valid in 2009-2010) information about customising what were the standard web pages in versions of Cumulus 1 up to 1.8.x. The translations there are NOT compatible with later (or final) Cumulus 1 version, nor will they work with Cumulus MX.'''
Line 305: Line 305:
On the downloads page you can find third-party alternative web pages, these typically include some language translation modules, but beware that these may not be maintained to work with latest versions of Cumulus.
On the downloads page you can find third-party alternative web pages, these typically include some language translation modules, but beware that these may not be maintained to work with latest versions of Cumulus.


== Can I connect/disconnect my weather station while Cumulus is running? ==
== Can I connect/disconnect my weather station while Cumulus 1 is running? ==
No. You must make sure your weather station is connected to your PC and switched on, before running Cumulus. Do not disconnect your station while Cumulus is running.
 
No. You must make sure your weather station is connected to your PC and switched on, before running Cumulus 1. Do not disconnect your station while Cumulus 1 is running.


== How does Cumulus deal with extra sensors? ==
== How does Cumulus deal with extra sensors? ==


By default, Cumulus deals with weather stations incorporating solar sensors, if you have selected the relevant station 'Type' or 'Display solar/extra data' in configuration, but it has some capability to deal with extra sensors added including the Blake-Larsen Sun Recorder.
By default, Cumulus 1 deals with weather stations incorporating solar sensors, if you have selected the relevant station 'Type' or 'Display solar/extra data' in configuration, but it has some capability to deal with extra sensors added including the Blake-Larsen Sun Recorder.
Cumulus has the ability to input, log, and display Current Values/Outputs from the [[Rain_measurement#Optical_Rain_Gauges|Hydreon Optical Rain Sensor - Model RG-11]] and from either Oregon Scientific or Davis [[Extra_Sensor_Files|extra sensors]]. Only today's and yesterday's total rainfall from a Hydreon sensor are available in [[today.ini]] and [[yesterday.ini]] respectively. For some Oregon Scientific models, the temperature from an extra sensor can replace the temperature from the main sensor for processing by Cumulus, but all extra sensor values are stored in a series of [[Extra_Sensor_Files| monthly log]] files. No other processing is performed for Davis extra sensors, but past values are retained in a series of [[Extra_Sensor_Files| monthly log]] files.  The file [[strings.ini]] is used to customise the description associated with extra sensors.
 
Cumulus 1 has the ability to input, log, and display Current Values/Outputs from the [[Rain_measurement#Optical_Rain_Gauges|Hydreon Optical Rain Sensor - Model RG-11]] and from either Oregon Scientific or Davis [[Extra_Sensor_Files|extra sensors]]. Only today's and yesterday's total rainfall from a Hydreon sensor are available in [[today.ini]] and [[yesterday.ini]] respectively.  
 
For some Oregon Scientific models, the temperature from an extra sensor can replace the temperature from the main sensor for processing by Cumulus 1, but all extra sensor values are stored in a series of [[Extra_Sensor_Files| monthly log]] files for extra sensors.  
 
No other processing is performed for Davis extra sensors, but past values are retained in a series of [[Extra_Sensor_Files|extra sensor monthly log]] files.  The file [[strings.ini]] is used to customise the description associated with extra sensors.


== What is this "Solar Max" value which Cumulus is displaying? ==
== What is this "Solar Max" value which Cumulus is displaying? ==
Line 323: Line 329:
You don't need to, and it's much safer if you don't; clearing the memory could lead to a loss of data. The memory indicator on the console has no effect on the logging of data; the console will automatically start re-using the oldest memory locations. As long as you are running Cumulus (at least occasionally), Cumulus will have downloaded the data it needs from the console, so the console is free to overwrite the oldest data when it needs to.
You don't need to, and it's much safer if you don't; clearing the memory could lead to a loss of data. The memory indicator on the console has no effect on the logging of data; the console will automatically start re-using the oldest memory locations. As long as you are running Cumulus (at least occasionally), Cumulus will have downloaded the data it needs from the console, so the console is free to overwrite the oldest data when it needs to.


== How do I get my Davis station with USB working with Cumulus? ==
== How do I get my Davis station with USB working with Cumulus 1? ==


{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
Line 348: Line 354:
this utility, select Convert USB to Virtual Serial in your WeatherLink program group on the Start menu of your computer (Start>AllPrograms>WeatherLink>Convert USB to Virtual Serial) and run the utility to convert your data logger. Please contact Davis Technical Support (“Contacting Davis Technical Support” on page 26) for more information."
this utility, select Convert USB to Virtual Serial in your WeatherLink program group on the Start menu of your computer (Start>AllPrograms>WeatherLink>Convert USB to Virtual Serial) and run the utility to convert your data logger. Please contact Davis Technical Support (“Contacting Davis Technical Support” on page 26) for more information."


== Why does Cumulus do some things the way it does, when there are better ways? ==
== Why does Cumulus 1 do some things the way it does, when there are better ways? ==


{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1
{{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1


Cumulus was originally something Steve Loft 'knocked together' quickly when I got my first weather station, simply because I couldn't find any other software anywhere which I was prepared to use. No 'design' went into it, it was really just a prototype. Some of the things I did were just quick 'hacks' that I intended to fix when I did it 'properly'. But I never got around to going back and doing it 'properly', and it was never my intention that anyone else would use it. But I was persuaded to make it available for others, and then to add more and more enhancements.  
''This text is by the author, Steve Loft''
 
Cumulus was originally something I 'knocked together' quickly when I got my first weather station, simply because I couldn't find any other software anywhere which I was prepared to use.  
 
No 'design' went into it, it was really just a prototype. Some of the things I did were just quick 'hacks' that I intended to fix when I did it 'properly'. But I never got around to going back and doing it 'properly', and it was never my intention that anyone else would use it. But I was persuaded to make it available for others, and then to add more and more enhancements.  


The fact that it works with several different types of weather station means that much of it is a compromise; it doesn't use certain features of the weather station which it could use if it were dedicated to that type of weather station. For example, it typically does not use any high/low data that the station might store internally. Instead, it maintains its own high/low data from individual readings. There are a number of reasons for this; the fact that Cumulus supports an 0900-0900 day, and the weather station does not, and the fact that typically Cumulus maintains far more high/low values than the station does, and these need to be self-consistent.  
The fact that it works with several different types of weather station means that much of it is a compromise; it doesn't use certain features of the weather station which it could use if it were dedicated to that type of weather station. For example, it typically does not use any high/low data that the station might store internally. Instead, it maintains its own high/low data from individual readings. There are a number of reasons for this; the fact that Cumulus supports an 0900-0900 day, and the weather station does not, and the fact that typically Cumulus maintains far more high/low values than the station does, and these need to be self-consistent.  


So yes, I am aware that some of things that Cumulus does may seem strange, but it is simply not possible for me to start again from scratch, knowing what I know now. And it is not possible for me to effectively produce separate versions of Cumulus specifically for each type of weather station. If you don't like the way Cumulus does certain things, do what I did and write your own software!
So yes, I am aware that some of things that Cumulus does may seem strange, but it is simply not possible for me to start again from scratch, this is done in my spare time.


== Can I run 2 copies of Cumulus? ==
And it is not possible for me to effectively produce separate versions of Cumulus specifically for each type of weather station. If you don't like the way Cumulus does certain things, do what I did and write your own software!
 
== Can I run 2 copies of Cumulus 1? ==


3 options:
3 options:
*You can install Cumulus 1 (or MX) on more than one machine, but each copy must connect directly to its own weather station (one station connected per Cumulus installation).
*You can install Cumulus 1 (or MX) on more than one machine, but each copy must connect directly to its own weather station (one station connected per Cumulus installation).
*You can install 2 copies of Cumulus 1 in different paths on a single PC, ''if you have two weather stations'' and Cumulus is able to distinguish between them, e.g. they are from different manufacturers, or both are serial port stations (different ports), or one is USB and one is serial, or one is a Weatherlink IP. In other words the  combination that does not work on a single PC is two USB stations (including clones from different suppliers) from the same manufacturer. Note that Davis stations with USB loggers are serial port stations as far as Cumulus is concerned, so there are no problems using multiple copies of Cumulus with multiple Davis stations on the same PC. (Same rules for two copies of Cumulus MX).
*You can install 2 copies of Cumulus 1 in different paths on a single PC, ''if you have two weather stations'' and Cumulus is able to distinguish between them, e.g. they are from different manufacturers, or both are serial port stations (different ports), or one is USB and one is serial, or one is a Weatherlink IP. In other words the  combination that does not work on a single PC is two USB stations (including clones from different suppliers) from the same manufacturer. Note that Davis stations with USB loggers are serial port stations as far as Cumulus is concerned, so there are no problems using multiple copies of Cumulus with multiple Davis stations on the same PC. (Same rules for two copies of Cumulus MX).
*It is possible to back up the Cumulus files from one installation running off a weather station, and briefly have another reduced functionality copy just looking at historic data without ever any updating (the second Cumulus is set up as if reading from an EasyWeather.dat file, but not given a path/file name) - see [[Cumulus.ini#Introduced_for_problems_with_Fine_Offset_family:|Easyweather.dat section here]].
*It is possible to back up the Cumulus files from one installation running off a weather station, and briefly have another reduced functionality copy just looking at historic data without ever any updating (the second Cumulus is set up as if reading from an EasyWeather.dat file, but not given a path/file name) - see [[Cumulus.ini_(Cumulus_1)#Introduced_for_problems_with_Fine_Offset_family:|Easyweather.dat section here]].


Don't attempt to run Cumulus 1 and MX at same time, they cannot share a single weather station. However you can with a single weather station, stop Cumulus 1 and then run MX if they use different data folders, then later stop MX and run Cumulus 1.
Don't attempt to run Cumulus 1 and MX at same time, they cannot share a single weather station. However you can with a single weather station, stop Cumulus 1 and then run MX if they use different data folders, then later stop MX and run Cumulus 1.
Line 383: Line 395:
== I installed a new version and my web page templates got over-written  ==
== I installed a new version and my web page templates got over-written  ==


{{Version badge 1}}The supplied web page templates are part of Cumulus and will be over-written on upgrade. If you want to create your own web pages, don’t edit the supplied ones, place them in a different folder and use the ‘extra files’ facility. From version 1.8.9, the installer offers the option of not over-writing the web templates; it unconditionally also installs them to a sub-folder of the web folder called 'originals', so you can refer to them if required, even if you chose not to over-write those in the web folder.
{{Version badge 1}}The supplied web page templates are part of Cumulus and will be over-written on upgrade.  
*If you want to create your own web pages, don’t edit the supplied ones, place your templates in a different folder and use the ‘extra files’ facility.  
*From version 1.8.9, the installer offers the option of not over-writing the web templates; it unconditionally also installs them to a sub-folder of the web folder called 'originals', so you can refer to the originals if required, even if you chose the new option not to over-write whatever template files are already being processed in the web folder.


== I can’t find my data files!  ==
== I can’t find my data files!  ==


{{Version badge 1}}You’re probably running Windows Vista/Windows 7/Windows 8 (or one of the corresponding server versions of Windows). Look in C:\Users\[username]\AppData\Local\VirtualStore\Program Files\Cumulus - note that this is a 'hidden' folder. Ideally, to avoid this situation, you would install to somewhere outside the Program Files hierarchy, as recommended in the readme.txt.
{{Version badge 1}}You’re probably running Windows Vista/Windows 7/Windows 8 (or one of the corresponding server versions of Windows). Look in C:\Users\[username]\AppData\Local\VirtualStore\Program Files\Cumulus - note that this is a 'hidden' folder. Ideally, to avoid this situation, you would install to somewhere outside the Program Files hierarchy, as recommended in the '''readme.txt'''.


== I can't save my NOAA reports! ==
== I can't save my NOAA reports! ==


{{Version badge 1}}You've probably corrupted your Cumulus.ini file in the default Cumulus folder. See [[Cumulus.ini#Section:_NOAA]]. It can only be edited either (if Cumulus is stopped) with an external text file editor or (with Cumulus running) using the ''NOAA Setup'' in the configuation menu.  Pay attention to where the quotes are required for the file names, and check that you have an allowed date format (see [[Webtags#Time.2FDate_.27format.27_Parameter]]).
{{Version badge 1}}You've probably corrupted your Cumulus.ini_(Cumulus_1) file in the default Cumulus folder. See [[Cumulus.ini_(Cumulus_1)#Section:_NOAA]]. It can only be edited either (if Cumulus is stopped) with an external text file editor or (with Cumulus running) using the ''NOAA Setup'' in the configuation menu.  Pay attention to where the quotes are required for the file names, and check that you have an allowed date format (see [[Webtags#The_format_used_for_naming]]).


== My sunrise and sunset times are wrong  ==
== My sunrise and sunset times are wrong  ==


You've almost certainly entered your co-ordinates incorrectly, or not entered them at all - on the station settings screen. You must enter DEGREES, MINUTES, and SECONDS, no other format will work. Make sure to use '''unsigned whole numbers''' for degrees, minutes, and seconds, with a 'W' for your longitude if you're West of the Greenwich meridian (e.g. if you are in the United States), and the appropriate letter for your latitude (N for northern hemisphere, S for southern hemisphere).  
You've almost certainly entered your co-ordinates incorrectly, or not entered them at all - on the station settings screen.  
*You must enter DEGREES, MINUTES, and SECONDS, no other format will work.  
*Make sure to use '''unsigned whole numbers''' for degrees, minutes, and seconds, with a 'W' for your longitude if you're West of the Greenwich meridian (e.g. if you are in the United States), and the appropriate letter for your latitude (N for northern hemisphere, S for southern hemisphere).  


If you are not familiar with the degrees/minutes/seconds standard format and have your co-ordinates in some other format, there are pages on the web which will convert for you. One such is here: http://transition.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html
If you are not familiar with the degrees/minutes/seconds standard format and have your co-ordinates in some other format, there are pages on the web which will convert for you. One such is here: http://transition.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html
Line 419: Line 435:
**You can try the same cure, but may not be able to recover the lost information in this case.
**You can try the same cure, but may not be able to recover the lost information in this case.


If you are viewing or editing log files at the time when rollover takes place, it is likely that some parts of the daily rollover will fail.  Although Cumulus 1 provides the functionality to view and (except for the data file) update the log files, make sure you have exited out of the built-in viewer or editor before rollover is due. If you inadvertently forget this, the cure of overwriting files mentioned above is applicable if your weather station has an internal log and it is around 2 logging intervals (see [[#Cumulus_takes_a_long_time_to_download_the_data_from_my_Davis_station_at_start_up]]) after rollover. When using an external editor, close Cumulus 1 or Cumulus MX before opening any Cumulus file.
If you are viewing or editing log files at the time when rollover takes place, it is likely that some parts of the daily rollover will fail.   
*Cumulus 1 provides the functionality to view any log file and you can update the log files that contain extreme records or the daily summary.
*Do make sure you have exited out of the built-in viewer or editor before rollover is due.  
**If you inadvertently forget this, the cure of overwriting files mentioned above is applicable if your weather station has an internal log and it is around 2 logging intervals (see [[#Cumulus_takes_a_long_time_to_download_the_data_from_my_Davis_station_at_start_up]]) after rollover.  
*When using an external editor, close Cumulus 1 or Cumulus MX before opening any Cumulus file.


== Why do I have some unexpected zero figures? ==
== Why do I have some unexpected zero figures? ==
Line 467: Line 487:


== Cumulus read some invalid figures from my station ==
== Cumulus read some invalid figures from my station ==
If you have:
If you have:
*just started using Cumulus,  
*just started using Cumulus,  
Line 473: 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 479: Line 500:
Over successive versions of Cumulus more and more code has been incorporated to deal with the way some stations are prone to reporting rogue readings.
Over successive versions of Cumulus more and more code has been incorporated to deal with the way some stations are prone to reporting rogue readings.
*Ensure you are using the latest Cumulus build, if you are using an old version you will not have any enhancements made since the earlier build that might improve the way Cumulus reads from your station type.
*Ensure you are using the latest Cumulus build, if you are using an old version you will not have any enhancements made since the earlier build that might improve the way Cumulus reads from your station type.
In general, if Cumulus 1.x.x identifies an odd value it will reuse the last good value instead, assuming that the problem will either right itself, or be spotted and dealt with quickly.
In general, if Cumulus 1.x.x identifies an odd value for up to 6 times, it will reuse the last good value instead. Depending on how frequently Cumulus is able to read from your station, that can represent
up to 5 minutes. That is designed to be long enough for you to spot the problem and deal with it. Sometimes the problem will right itself within that time. After that time, a problem with reading temperature, humidity, wind, or pressure, means Cumulus cannot calculate derived values, the last successful read is considered too stale to reuse, and by default Cumulus will stop any further processing.


'''Fine Offset stations''' are prone to reporting the odd non-sensical value, and Cumulus has the ability to compare successive readings:
'''Fine Offset stations''' are prone to reporting the odd nonsensical value, and Cumulus has the ability to compare successive readings:
*From the '''Configuration''' menu select [[Cumulus_Screenshots#Configuration_Menu_Screens|''Calibration'']] and in the '''Spike removal''' frame you can specify "the maximum '''differences''' between successive values" that Cumulus is to tolerate. See the '''Help''' for that screen, and note that spike removal applies while Cumulus is running, not to catch-up readings from the station's logger.  
*{{Version badge 1}}From the '''Configuration''' menu select [[Cumulus_Screenshots#Configuration_Menu_Screens|''Calibration'']] and in the '''Spike removal''' frame you can specify "the maximum '''differences''' between successive values" that Cumulus is to tolerate.  
*{{Version badge 1}}See the '''Help''' for that screen, and note that '''spike removal applies while Cumulus is running''', it is not applied to catch-up readings from the station's logger.  


'''Possible Cure:'''
'''Possible Cure:'''
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 [[Diags]] 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 occured, 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_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 522: Line 545:
Because many positive values are realistic, Cumulus generally will accept those odd increases as a result of accidental knocking of a tipping bucket gauge, due to wind effects on the gauge, or even due to the station electronics generating a rogue reading. The sub-answers below explain how to correct such errors.
Because many positive values are realistic, Cumulus generally will accept those odd increases as a result of accidental knocking of a tipping bucket gauge, due to wind effects on the gauge, or even due to the station electronics generating a rogue reading. The sub-answers below explain how to correct such errors.
=== (Invented rain) Error in today's total ===
=== (Invented rain) Error in today's total ===
Easy - correct today's total using the [[Today.ini#Editing_rainfall_in_today.ini_within_Cumulus | 'today's rain']] editor on the edit menu (select from main screen in Cumulus 1, or find in the MX browser interface).
Easy - correct today's total using the [[Today.ini#Editing_rainfall_in_today.ini_within_Cumulus | 'today's rain']] editor on the edit menu (select from main screen in Cumulus 1, or find in the MX admin interface).


=== (Invented rain) Error in date/time of 'Last Tip' ===
=== (Invented rain) Error in date/time of 'Last Tip' ===
Line 528: Line 551:


=== (Invented rain) Error in number of consecutive days with or without rain ===
=== (Invented rain) Error in number of consecutive days with or without rain ===
# The counts are for completed days, not part days. The threshold for whether a day counts as a wet day is set in the optional parameter [[Cumulus.ini#Section:_Station|RainDayThreshold= -1]], and the parameter [[Cumulus.ini#Section:_Station|NoFlashWetDryDayRecords=1]] is also relevant.
# The counts are for completed days, not part days. The threshold for whether a day counts as a wet day is set in the optional parameter [[Cumulus.ini_(Cumulus_1)#Section:_Station|RainDayThreshold= -1]], and the parameter [[Cumulus.ini_(Cumulus_1)#Section:_Station|NoFlashWetDryDayRecords=1]] is also relevant.
# Remember that 'ConsecutiveDryDays' and 'ConsecutiveWetDays' do not include today, they reflect the daily rainfall amounts stored in the [[dayfile.txt|daily summary log]].
# Remember that 'ConsecutiveDryDays' and 'ConsecutiveWetDays' do not include today, they reflect the daily rainfall amounts stored in the [[dayfile.txt|daily summary log]].


Line 564: Line 587:
Note that other rain figures, such as 'rain last hour', 'rain last 24 hours' and 'rain since midnight' depend on a sensible progression of the rain counter described in previous sub-answer, so it's not easy to correct this; it is easier to wait until the erroneous figure is far enough in the past so as not to affect the calculation of these 3 other values. Note that if you're using a midnight start of day then you don't need the 'rain since midnight' figure anyway, as it is normally the same as 'rain today', and that figure is much more easily corrected.
Note that other rain figures, such as 'rain last hour', 'rain last 24 hours' and 'rain since midnight' depend on a sensible progression of the rain counter described in previous sub-answer, so it's not easy to correct this; it is easier to wait until the erroneous figure is far enough in the past so as not to affect the calculation of these 3 other values. Note that if you're using a midnight start of day then you don't need the 'rain since midnight' figure anyway, as it is normally the same as 'rain today', and that figure is much more easily corrected.


If you really do want to try to correct these other rain figures; you would need to stop Cumulus, then find (for the period in question), the correct [[monthly_log_files|monthly log file]] field 11 (assuming date is field 0), which stores the Cumulus 'rain counter' values, and edit (increasing the value in the count field, decreases the difference to the next (or current) count, and therefore reduces the rain in the in-between period) so they are correct relative to the current value of the rain counter (i.e. the latest one logged).
If you really do want to try to correct these other rain figures; you would need to stop Cumulus, then find (for the period in question), the correct [[Standard_log_files|standard log file]] field 11 (assuming date is field 0), which stores the Cumulus 'rain counter' values, and edit (increasing the value in the count field, decreases the difference to the next (or current) count, and therefore reduces the rain in the in-between period) so they are correct relative to the current value of the rain counter (i.e. the latest one logged).


===  (Invented rain) Error prevention by Spike removal ===
===  (Invented rain) Error prevention by Spike removal ===
Line 590: Line 613:
In all cases,  wait until Cumulus has written the next log entry (i.e. wait the number of minutes that you have set as the Cumulus logging interval), then restart Cumulus to get the monthly and annual totals recalculated from correct daily totals.  
In all cases,  wait until Cumulus has written the next log entry (i.e. wait the number of minutes that you have set as the Cumulus logging interval), then restart Cumulus to get the monthly and annual totals recalculated from correct daily totals.  


If you need to correct within day values for trend graphs as well as the longer period totals, provided you know roughly when the rogue rainfall was recorded, find (and edit) it in the [[monthly_log_files]], field 11 (assuming date is field 0) is the count used to derive other parameters. Increasing the value in the count field, decreases the difference to the next (or current) count, and therefore reduces the rain in the in-between period.
If you need to correct within day values for trend graphs as well as the longer period totals, provided you know roughly when the rogue rainfall was recorded, find (and edit) it in the [[Standard_log_files]], field 11 (assuming date is field 0) is the count used to derive other parameters. Increasing the value in the count field, decreases the difference to the next (or current) count, and therefore reduces the rain in the in-between period.


== The ‘gust’ line has disappeared from my graph  ==
== The ‘gust’ line has disappeared from my graph  ==
Line 606: Line 629:
If you do this, you will probably need to edit your log files in the '''data''' folder as you may have duplicate entries and/or entries out of order. Your rain totals will almost certainly also be wrong - the total for "today" in particular. See the [[FAQ#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 |FAQ]] entry about correcting rainfall data. If you have only just started using Cumulus, you could delete all of the files in the data folder, and just create a simple today.ini as below. Then when you start Cumulus, processing will start again with just the data from the station's logger.
If you do this, you will probably need to edit your log files in the '''data''' folder as you may have duplicate entries and/or entries out of order. Your rain totals will almost certainly also be wrong - the total for "today" in particular. See the [[FAQ#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 |FAQ]] entry about correcting rainfall data. If you have only just started using Cumulus, you could delete all of the files in the data folder, and just create a simple today.ini as below. Then when you start Cumulus, processing will start again with just the data from the station's logger.


Note that this method does not work for the Oregon WMR200 station. This station deletes logger entries when they are downloaded, and there is no mechanism for retrieving logger entries for a particular period - it just sends all the entries that it has. You may be able to circumvent this by creating a today.ini file in the data folder before you run Cumulus 1, with just this in it:
Note that this method does not work for the Oregon WMR200 station. This station deletes logger entries when they are downloaded, and there is no mechanism for retrieving logger entries for a particular period - it just sends all the entries that it has. {{Version badge 1}}You may be able to circumvent this by creating a today.ini file in the data folder before you run Cumulus 1, with just this in it:
<pre>
<pre>
[General]
[General]
Line 615: Line 638:
CurrentDay=10
CurrentDay=10
</pre>
</pre>
Note that Cumulus MX stores some time-stamps '''in ISO format''' (yyyy/MM/dd HH:mm:ss) within '[[today.ini]]', the format example above only works for Cumulus 1, see the article on the log file itself for specifics.
Note that Cumulus MX stores some time-stamps '''in ISO format''' (yyyy/MM/dd HH:mm:ss) within '[[today.ini]]', the format example above only works for {{Version badge 1}}Cumulus 1, see the article on the log file itself for specifics.
Change the dates and time to match the point from which you want Cumulus to start downloading data. If the station has already sent the data, this may not work, unfortunately.
Change the dates and time to match the point from which you want Cumulus to start downloading data. If the station has already sent the data, this may not work, unfortunately.


Line 626: Line 649:
== I have inserted pre-Cumulus data making 'Records began on' date wrong ==
== I have inserted pre-Cumulus data making 'Records began on' date wrong ==


Stop Cumulus and edit [[Cumulus.ini#Section:_Station | Cumulus.ini (station section)]] within the main Cumulus folder. Change the "StartDate=" line. Be sure to use the same format for the date.
Stop Cumulus and edit [[Cumulus.ini_(Cumulus_1)#Section:_Station | Cumulus.ini_(Cumulus_1) (station section)]] within the main Cumulus folder. Change the "StartDate=" line. Be sure to use the same format for the date.


{{Version badge 1}}'''Note''' ''StartDate=xxxx'' does ''not'' need to be updated for Cumulus 1 to recognise earlier data in log files in its ''data'' subfolder.   
{{Version badge 1}}'''Note''' ''StartDate=xxxx'' does ''not'' need to be updated for Cumulus 1 to recognise earlier data in log files in its ''data'' subfolder.   


[[File:Badge vMx.png]] However in calculating and updating extremes, Cumulus MX will ignore any monthly log file data prior to the start date set, so it is crucial to make sure the start date is right before you (re-)start MX.
[[File:Badge vMx.png]] However in calculating and updating extremes, '''CumulusMX.exe''' will ignore any standard log file for any month prior to the start date set, so it is crucial to make sure the start date is right before you (re-)start MX. However, if you use '''ExportMySQL.exe monthly''' this will start with January 2000 and process any standard log found for any month after that.


{{Version badge 1}}It really represents "Cumulus began on", so there is an alternative of leaving cumulus.ini unchanged, but editing default Cumulus ''recordsT.htm'' template twice:
{{Version badge 1}}and [[File:Badge vMx.png]]There is one web page template file ''recordT.htm'' that in two places uses this date. If you want to make one of those be the earliest date you  now have for your data and the other one to be when you started using Cumulus; there is an alternative of leaving '''Cumulus.ini_(Cumulus_1)''' unchanged, but editing the ''recordT.htm'' template twice:
*after the h2 heading is ''&lt;p&gt;Records began on <#recordsbegandate>. Here are the extremes recorded since then.&lt;/p&gt;'';  you can replace '<#recordsbegandate>' with the new earliest date typed in as text; and
*after the h2 heading is ''&lt;p&gt;Records began on <#recordsbegandate>. Here are the extremes recorded since then.&lt;/p&gt;'';  you can replace '<#recordsbegandate>' with the new earliest date typed in as text; and
*at the start of the table is the ''&lt;caption&gt;Records Since <#recordsbegandate>&lt;/caption&gt;''; replace the label "Records since" with "Cumulus began on" leaving the web tag unchanged.
*at the start of the table is the ''&lt;caption&gt;Records Since <#recordsbegandate>&lt;/caption&gt;''; replace the label "Records since" with "Cumulus began on" leaving the web tag unchanged.
Line 641: Line 664:
# that you are comparing the Cumulus display with the ‘relative’ pressure on your console,
# that you are comparing the Cumulus display with the ‘relative’ pressure on your console,
# that only one copy of Cumulus is accessing the weather station (and no other software),
# that only one copy of Cumulus is accessing the weather station (and no other software),
# that you do not have a 'EWpressureoffset=x.y' line in the [Station] section of [[Cumulus.ini#Introduced_for_problems_with_Fine_Offset_family:| cumulus.ini]],
# that you do not have a 'EWpressureoffset=x.y' line in the [Station] section of [[Cumulus.ini_(Cumulus_1)#Introduced_for_problems_with_Fine_Offset_family:| cumulus.ini]],
# and that you do not have a setting for pressure on the Cumulus calibration screen.
# and that you do not have a setting for pressure on the Cumulus calibration screen.


The Fine Offset stations only store absolute/station pressure readings in their weather memory locations updated with each transmission and read by Cumulus. Within Cumulus, the software applies the adjustment to sea level before any further processing. It does ''not'' use the altitude setting in the cumulus station configuration screen.
The Fine Offset stations only store absolute/station pressure readings in their weather memory locations updated with each transmission and read by Cumulus. Within Cumulus, the software applies the adjustment to sea level before any further processing. It does ''not'' use the altitude setting in the cumulus station configuration screen.
Normally when Cumulus starts, it reads in [http://www.jim-easterbrook.me.uk/weather/mm/ the fixed block] in the console a pair of absolute/station pressure and relative/sea level pressure readings and uses the difference between these as the ‘offset’ in millibar for the station;  Cumulus uses this offset subsequently to calculate the sea level pressure (each time when reading the absolute pressure in the weather memory locations of the station), but it is possible to define the offset in '''Cumulus.ini''' instead.  
Normally when Cumulus starts, it reads in [http://www.jim-easterbrook.me.uk/weather/mm/ the fixed block] in the console a pair of absolute/station pressure and relative/sea level pressure readings and uses the difference between these as the ‘offset’ in millibar for the station;  Cumulus uses this offset subsequently to calculate the sea level pressure (each time when reading the absolute pressure in the weather memory locations of the station), but it is possible to define the offset in '''Cumulus.ini_(Cumulus_1)''' instead.
 
{{Version badge 1}}'''IMPORTANT'''  These notes apply to Cumulus 1.  '''bvs79669''' did some investigation in January 2019 that reveals the ''mapping of memory bytes to pressure reported by Jim Easterbrook and used by Steve Loft is wrong''. The two most significant bits included in that mapping as being part of the pressure output should not be included as they create impossibly high readings for pressure. From build 3047, MX excludes these two bits when reading the pressure and the reliability of reading correct pressure from a Fine Offset station has been significantly improved.


Make sure that you have set your console's relative pressure correctly:
Make sure that you have set your console's relative pressure correctly:
Line 714: 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 Diags folder 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.
{{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 791: 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 803: Line 828:
This is an attempt to make sure that bad data is not logged. If your weather station is not fully functional, you will not be able to use Cumulus fully.  
This is an attempt to make sure that bad data is not logged. If your weather station is not fully functional, you will not be able to use Cumulus fully.  


You can over-ride the start up check by adding a line to the [Station] section of [[Cumulus.ini#Section:_Station|cumulus.ini]], thus: ''NoSensorCheck=1''
You can over-ride the start up check by adding a line to the [Station] section of [[Cumulus.ini_(Cumulus_1)#Section:_Station|cumulus.ini]], thus: ''NoSensorCheck=1''
(You need to do this while Cumulus is stopped). Note that you are likely to get bad data logged if you do this.
(You need to do this while Cumulus is stopped). Note that you are likely to get bad data logged if you do this.


Line 847: Line 872:


== How do I correct my all-time (or monthly all-time) records? ==
== How do I correct my all-time (or monthly all-time) records? ==
Cumulus works by whenever the reading it is currently processing exceeds a particular record, that record is updated. In essence, Cumulus end-of-day works by reading what is in the detailed [[Monthly_log_files]] to find the highs and lows during the day just ended, these then update the [[dayfile.txt|daily summary log]]. Cumulus can also read what is in the daily summary log to update the all-time extremes held in [[alltime.ini]] and month-by-month all-time extremes held in [[monthlyalltime.ini]]. Look up those cross-references to help you understand the various items, and how they can be updated.
Cumulus works by whenever the reading it is currently processing exceeds a particular record, that record is updated. In essence, Cumulus end-of-day works by reading what is in the monthly [[Standard_log_files]] to find the highs and lows during the day just ended, these then update the [[dayfile.txt|daily summary log]]. Cumulus can also read what is in the daily summary log to update the all-time extremes held in [[alltime.ini]] and month-by-month all-time extremes held in [[monthlyalltime.ini]]. Look up those cross-references to help you understand the various items, and how they can be updated.


Either 1) Consequently, you can manually copy the sequence remembering it requires several steps:
Either 1) Consequently, you can manually copy the sequence remembering it requires several steps:
# Correct the rogue values or values in the detailed [[Monthly_log_files]] ''with Cumulus stopped''. Neither Cumulus 1 nor Cumulus MX provides an editor to do this, and you need to guess new values for readings as there is no other file provided by Cumulus to offer any suggestions, often people interpolate between earlier and later readings.
# Correct the rogue values or values in the monthly [[Standard_log_files]] ''with Cumulus stopped''. Neither Cumulus 1 nor Cumulus MX provides an editor to do this, and you need to guess new values for readings as there is no other file provided by Cumulus to offer any suggestions, often people interpolate between earlier and later readings.
# Correct the [[dayfile.txt|daily summary log]] ''(don't do this near the rollover time)'', the editor in Cumulus 1 requires you to manually change the numbers, unless you delete the whole day (or it was previously missing) and you ask Cumulus to '''Insert missing''' i.e. populate a single line (day) from the detailed log, ignoring any extremes at times between logged readings.
# Correct the [[dayfile.txt|daily summary log]] ''(don't do this near the rollover time)'', the editor in Cumulus 1 requires you to manually change the numbers, unless you delete the whole day (or it was previously missing) and you ask Cumulus to '''Insert missing''' i.e. populate a single line (day) from the detailed log, ignoring any extremes at times between logged readings.
# Correct the all-time extremes held in [[alltime.ini]] and monthly all-time extremes held in [[monthlyalltime.ini]]. Using the Cumulus 1 [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu|built-in appropriate editor]] from the first couple of commands in the Edit menu (and now also in CumulusMX) allows you to see, and copy across, suggested extremes based on contents of the detailed [[Monthly_log_files]] or contents of  the [[dayfile.txt|daily summary log]].
# Correct the all-time extremes held in [[alltime.ini]] and monthly all-time extremes held in [[monthlyalltime.ini]]. Using the Cumulus 1 [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu|built-in appropriate editor]] from the first couple of commands in the Edit menu (and now also in CumulusMX) allows you to see, and copy across, suggested extremes based on contents of the monthly [[Standard_log_files]] or contents of  the [[dayfile.txt|daily summary log]].


or 2) If you know the correct figures, you can alternatively enter them manually directly into the .ini files and not bother to update the detailed log or the daily summary log. (It is pointless to edit the .ini files directly and then afterwards edit the log files):
or 2) If you know the correct figures, you can alternatively enter them manually directly into the .ini files and not bother to update the detailed log or the daily summary log. (It is pointless to edit the .ini files directly and then afterwards edit the log files):
Line 871: 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 diags 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:
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_(Cumulus_1). In the [Station] section, add a line:


FOReadAvoidPeriod=N
FOReadAvoidPeriod=N
Line 940: Line 965:
*From b3068 CumulusMX can be started with the -debug parameter to switch on debug and data logging from start-up. This is often the best option.
*From b3068 CumulusMX can be started with the -debug parameter to switch on debug and data logging from start-up. This is often the best option.
*Whilst MX is running the logging can be switched off/on via the administrator interface - Settings|Station settings|Options ''Debug logging'' & ''Data logging''
*Whilst MX is running the logging can be switched off/on via the administrator interface - Settings|Station settings|Options ''Debug logging'' & ''Data logging''
*With MX stopped, edit Cumulus.ini. In the [Station] section set (or add if missing) the two entries...
*With MX stopped, edit Cumulus.ini_(Cumulus_1). In the [Station] section set (or add if missing) the two entries...
<pre>Logging=1
<pre>Logging=1
DataLogging=1</pre>
DataLogging=1</pre>
Line 1,037: Line 1,062:
     <td></td>
     <td></td>
</pre>
</pre>
*If you want to stop Cumulus uploading the indoor temperature graph, you can un-tick 'Include standard images' on the 'files' tab of the internet settings, and list all of the images that you still want to be uploaded as extra files. Cumulus 1 configuration only allows you to add 10 files so you would need to do this by editing Cumulus.ini, ironically these notes do not apply to Cumulus MX but in that all 100 slots can be edited within the settings pages.
*If you want to stop Cumulus uploading the indoor temperature graph, you can un-tick 'Include standard images' on the 'files' tab of the internet settings, and list all of the images that you still want to be uploaded as extra files. Cumulus 1 configuration only allows you to add 10 files so you would need to do this by editing Cumulus.ini_(Cumulus_1), ironically these notes do not apply to Cumulus MX but in that all 100 slots can be edited within the settings pages.
*To show solar instead, replace 'intemp.png' with 'solar.png', replace 'intempsm.png' with 'solarsm.png', and change the wording of the value associated with the alt property.
*To show solar instead, replace 'intemp.png' with 'solar.png', replace 'intempsm.png' with 'solarsm.png', and change the wording of the value associated with the alt property.
*To make Cumulus upload the solar graph, select it on the 'files' tab of the internet settings.
*To make Cumulus upload the solar graph, select it on the 'files' tab of the internet settings.
Line 1,138: 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 [[webtag]] 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|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.
*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  ==
Line 1,156: Line 1,181:
You'll need to list the (source) file including paths on the files tab of the internet settings, and specify a destination path and file name for the remote file in each case. Don't tick the ''FTP?'' box for standard cumulus pages (the exception is for a local web server and any non-standard web page that attempts to read using a script a local file such as dayfile.txt as this does need FTP to generate the server-based web page). For the standard images, you can supply a folder name (specify on the same screen), and they will all get copied there. See [[Customised_templates#What_to_select_on_the_.27Files.27_tab_of_the_Internet_Settings_screen_within_the_.27Configuration.27_menu|here]] for greater detail.
You'll need to list the (source) file including paths on the files tab of the internet settings, and specify a destination path and file name for the remote file in each case. Don't tick the ''FTP?'' box for standard cumulus pages (the exception is for a local web server and any non-standard web page that attempts to read using a script a local file such as dayfile.txt as this does need FTP to generate the server-based web page). For the standard images, you can supply a folder name (specify on the same screen), and they will all get copied there. See [[Customised_templates#What_to_select_on_the_.27Files.27_tab_of_the_Internet_Settings_screen_within_the_.27Configuration.27_menu|here]] for greater detail.


There's a limit of 10 entries on the files tab in Cumulus 1.9.x (in Cumulus MX all 100 entries are included in the settings interface).  Entries for the full 100 files can also be amended by editing [[Cumulus.ini#Section:_FTP_site|cumulus.ini]], with Cumulus stopped. Follow the format of any existing entries for specifying additional files.
There's a limit of 10 entries on the files tab in Cumulus 1.9.x (in Cumulus MX all 100 entries are included in the settings interface).  Entries for the full 100 files can also be amended by editing [[Cumulus.ini_(Cumulus_1)#Section:_FTP_site|cumulus.ini]], with Cumulus stopped. Follow the format of any existing entries for specifying additional files.


== Error Codes generated by FTP or Winsock ==
== Error Codes generated by FTP or Winsock ==
Sfws
5,838

edits

Retrieved from "https://www.cumuluswiki.org/a/Special:MobileDiff/6109...7983"

Navigation menu