Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Difficulty with Webtag <#DaysSince30Dec1899>
- krmidas
- Posts: 215
- Joined: Sat 03 Jul 2010 9:03 pm
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 10
- Location: Lake Zurich, IL; USA
- Contact:
Difficulty with Webtag <#DaysSince30Dec1899>
I'm trying to get a value for the total number of days my station has been in operation (June 18, 2005). I'm assuming I should use the webtag <#DaysSince30Dec1899> , replacing Dec 30, 1899 with June 18, 2005. I wasn't sure about the formatting of the month name so I also tried it with "Jun" as well as "June" but no success. Am I misunderstanding the purpose of this webtag?
-Tom
-Tom
-
water01
- Posts: 3670
- Joined: Sat 13 Aug 2011 9:33 am
- Weather Station: Ecowitt HP2551
- Operating System: Windows 10/11 64bit Synology NAS
- Location: Burnham-on-Sea
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
That webtag is exactly what it says it is Days since 30th December 1899. The webtag you should be using is #DaysSinceRecordsBegan.
- krmidas
- Posts: 215
- Joined: Sat 03 Jul 2010 9:03 pm
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 10
- Location: Lake Zurich, IL; USA
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Huh. What is the significance of Dec. 30, 1899?
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
It's the 'base' date for storing dates and times in some systems. See https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=8765
Steve
-
water01
- Posts: 3670
- Joined: Sat 13 Aug 2011 9:33 am
- Weather Station: Ecowitt HP2551
- Operating System: Windows 10/11 64bit Synology NAS
- Location: Burnham-on-Sea
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Mainframes (the old computers I started on in 1969!!) used to use the number of days since the 1st January 1900 as a means of holding dates, but this all got fouled up by the first popular spreadsheet Lotus 123 that had a bug in it for leap years and when Microsoft issued the first versions of Excel in 1995 it was decided in order to keep them compatible and correct the bug to use 30th December 1899!!
If you google you can find loads more info and yes a year with 2 zeros or more i.e. 1900 or 2000 is not a leap year according to the rules to calculate dates.Actually for the people here there is a little bit of a story about thus date choice.
Logically a good starting date with the January 1, 1900, so why a off that date?
It turns out that many years ago Lotus 123 was one of the more popular spreadsheets in the marketplace. It also turns out that Lotus 123 had a date calculation bug in which it assumed that the year 1900 was a leap year.
So for issues of compatibility and making the calculations remain the same across the two products, Excel by design and on purpose adopted the same date calculation bug!
So when they were setting up the date calculations system for VBA, there was a decision made to offset it by one day, as that would result in the same number of days between two different dates as what you get in Excel and Lotus.
So in theory I can't really say the above is 100% true, but they simply just offset it by one day to be different and to reduce the confusion issue.
There is some explains and details here:
http://www.cpearson.com/excel/datetime.htm
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
1900 wasn't a leap year, but 2000 was.water01 wrote:a year with 2 zeros or more i.e. 1900 or 2000 is not a leap year according to the rules to calculate dates.
Steve
-
RayProudfoot
- Posts: 3602
- Joined: Wed 06 May 2009 6:29 pm
- Weather Station: Davis VP2 with Daytime FARS
- Operating System: Windows XP SP3
- Location: Cheadle Hulme, Cheshire, England
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
IIRC if the year is exactly divisible by 50 it's a leap year.steve wrote:1900 wasn't a leap year, but 2000 was.water01 wrote:a year with 2 zeros or more i.e. 1900 or 2000 is not a leap year according to the rules to calculate dates.
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
No, 'century' years have to be divisible by 400 to be leap year. 1900 is divisible by 50 but isn't a leap year.RayProudfoot wrote:IIRC if the year is exactly divisible by 50 it's a leap year.steve wrote:1900 wasn't a leap year, but 2000 was.water01 wrote:a year with 2 zeros or more i.e. 1900 or 2000 is not a leap year according to the rules to calculate dates.
Steve
-
RayProudfoot
- Posts: 3602
- Joined: Wed 06 May 2009 6:29 pm
- Weather Station: Davis VP2 with Daytime FARS
- Operating System: Windows XP SP3
- Location: Cheadle Hulme, Cheshire, England
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Yep, that's it. I should have thought about it a bit more before posting.steve wrote:No, 'century' years have to be divisible by 400 to be leap year. 1900 is divisible by 50 but isn't a leap year.
- krmidas
- Posts: 215
- Joined: Sat 03 Jul 2010 9:03 pm
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 10
- Location: Lake Zurich, IL; USA
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Actually that won't help me either, since my station online date was before I started using Cumulus. I assume that webtag is hard-wired to show when Cumulus was first engaged, and can't be overwritten.water01 wrote:The webtag you should be using is #DaysSinceRecordsBegan.
-Tom
-
RayProudfoot
- Posts: 3602
- Joined: Wed 06 May 2009 6:29 pm
- Weather Station: Davis VP2 with Daytime FARS
- Operating System: Windows XP SP3
- Location: Cheadle Hulme, Cheshire, England
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Why not just hard-code your start date and forget webtags?
-
Matt.j5b
- Posts: 512
- Joined: Mon 28 Nov 2011 2:13 am
- Weather Station: Davis VP2/ WLL with DFARS
- Operating System: RPi Raspbian (Buster)
- Location: Ferny Grove, Brisbane, Australia
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
Stop Cumulus and edit the Cumulus.ini file. Adjust the date in the line starting with "StartDate=". Save the file and restart Cumulus as per here: https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=9670
- krmidas
- Posts: 215
- Joined: Sat 03 Jul 2010 9:03 pm
- Weather Station: Davis Vantage Pro 2
- Operating System: Windows 10
- Location: Lake Zurich, IL; USA
- Contact:
Re: Difficulty with Webtag <#DaysSince30Dec1899>
That should do it! Thanks.Matt.j5b wrote:Stop Cumulus and edit the Cumulus.ini file. Adjust the date in the line starting with "StartDate=". Save the file and restart Cumulus as per here: https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=9670