Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Station update not working
Moderator: mcrossley
-
- Posts: 17
- Joined: Wed 12 Aug 2020 2:53 am
- Weather Station: Aercus WS3085
- Operating System: Windows 10
Station update not working
Just installed latest Cumulus MX. Using Aercus WS3805 station and console. All worked OK in Cumulus 1.
Have connection OK to weather underground. Admin Dashboard shows data, but not refreshing, and station update does not refresh after startup. Have attached MX Diags folder as a ZIP, and three screen shots to help explain the problem. Any help much appreciated.
Thanks
Ron
Have connection OK to weather underground. Admin Dashboard shows data, but not refreshing, and station update does not refresh after startup. Have attached MX Diags folder as a ZIP, and three screen shots to help explain the problem. Any help much appreciated.
Thanks
Ron
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12763
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Station update not working
Could you switch on debug and data logging under Program Settings please. Restart, let MX run for 5 mins then post the latest log file again. Cheers.
-
- Posts: 17
- Joined: Wed 12 Aug 2020 2:53 am
- Weather Station: Aercus WS3085
- Operating System: Windows 10
Re: Station update not working
Thanks Mark
2 files attached - service console log and debug log.
Ron
2 files attached - service console log and debug log.
Ron
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12763
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Station update not working
Hmm, looks like a bug in CMX to me
I'll investigate....
I'll investigate....
-
- Posts: 76
- Joined: Fri 11 Mar 2011 2:04 am
- Weather Station: Ecowitt GW1103
- Operating System: windows 11 Pro/Raspberry pi 4
- Location: Brunswick Australia
Re: Station update not working
I have the WS3085 also, no problems with Windows 11 and using a separate console with Raspberry both refreshing OK
The log from rons47 shows different logging time on the console and CMX (2022-06-29 23:23:03.506 Warning, your console logging interval (30 mins) does not match the Cumulus logging interval (10 mins))
The log from rons47 shows different logging time on the console and CMX (2022-06-29 23:23:03.506 Warning, your console logging interval (30 mins) does not match the Cumulus logging interval (10 mins))
-
- Posts: 17
- Joined: Wed 12 Aug 2020 2:53 am
- Weather Station: Aercus WS3085
- Operating System: Windows 10
Re: Station update not working
Thanks for that.
I can't find where to set the console logging time. Cumulus 1 on Windows doesn't seem to have that configuration item. Any idea?
Ron
I can't find where to set the console logging time. Cumulus 1 on Windows doesn't seem to have that configuration item. Any idea?
Ron
-
- Posts: 76
- Joined: Fri 11 Mar 2011 2:04 am
- Weather Station: Ecowitt GW1103
- Operating System: windows 11 Pro/Raspberry pi 4
- Location: Brunswick Australia
Re: Station update not working
Easyweather software from Fine Offset
http://www.foshk.com/Support/software/34.html
Use it to configure the console and download data to a database (MS Access)
Don't run CMX at the same time
Click on the bottom Easyweather text
http://www.foshk.com/Support/software/34.html
Use it to configure the console and download data to a database (MS Access)
Don't run CMX at the same time
Click on the bottom Easyweather text
You do not have the required permissions to view the files attached to this post.
-
- Posts: 17
- Joined: Wed 12 Aug 2020 2:53 am
- Weather Station: Aercus WS3085
- Operating System: Windows 10
Re: Station update not working
Well A new day.
I ran the setlogger.exe utility, and set it to 10 minutes. Restarted Cumulus MX and now all seems to be working OK. Station update is now every 10 seconds, and the "now screen" looks good. Weather Underground is getting updated too (ICENTR233)
Let's leave this open and I'll confirm all is OK later today AU time.
I ran the setlogger.exe utility, and set it to 10 minutes. Restarted Cumulus MX and now all seems to be working OK. Station update is now every 10 seconds, and the "now screen" looks good. Weather Underground is getting updated too (ICENTR233)
Let's leave this open and I'll confirm all is OK later today AU time.
- mcrossley
- Posts: 12763
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Station update not working
TLDR: I don't recommend using the synchronise option on stations with solar sensors. It probably adds nothing and may be harmful on stations without solar sensors as well.
OK, there is a problem with the synchronisation code. It was written to take account of the 48 second data updates, however if you have a solar sensor it also updates at an independent 60 second period as well. This will mess up the timings completely. There is also a bug in the 48 second code that means it may fail to calculate the period accurately.
Regarding the setting of the station logger period, CMX has had the ability to do this built-in for a long time. If enabled, then at start-up if the station logger period does not match the CMX period the station period is changed.
OK, there is a problem with the synchronisation code. It was written to take account of the 48 second data updates, however if you have a solar sensor it also updates at an independent 60 second period as well. This will mess up the timings completely. There is also a bug in the 48 second code that means it may fail to calculate the period accurately.
Regarding the setting of the station logger period, CMX has had the ability to do this built-in for a long time. If enabled, then at start-up if the station logger period does not match the CMX period the station period is changed.
-
- Posts: 17
- Joined: Wed 12 Aug 2020 2:53 am
- Weather Station: Aercus WS3085
- Operating System: Windows 10
Re: Station update not working
Thanks for the advice Mark
Where in CMX do you set and enable the logger period. I didn't see that on the admin config screens.
Where in CMX do you set and enable the logger period. I didn't see that on the admin config screens.
- PaulMy
- Posts: 3848
- Joined: Sun 28 Sep 2008 11:54 pm
- Weather Station: Davis VP2 Plus 24-Hour FARS
- Operating System: Windows8 and Windows10
- Location: Komoka, ON Canada
- Contact:
Re: Station update not working
Hi,
I have a Davis station, so not a WS3085, and after selecting the Station type > Station settings, General Settings > click on my Davis station type > Advanced Options > Logger interval: Set the Davis Logger interval to match Cumulus MX interval
I have then tried it on a CMX test install by selecting a Fine Offset station type > Fine Offset Advanced Options > Set Logger Interval:
Set the FineOffset Logger interval to match Cumulus MX interval.
So this seems to show it correctly.
Enjoy,
Paul
I have a Davis station, so not a WS3085, and after selecting the Station type > Station settings, General Settings > click on my Davis station type > Advanced Options > Logger interval: Set the Davis Logger interval to match Cumulus MX interval
I have then tried it on a CMX test install by selecting a Fine Offset station type > Fine Offset Advanced Options > Set Logger Interval:
Set the FineOffset Logger interval to match Cumulus MX interval.
So this seems to show it correctly.
Enjoy,
Paul
VP2+
C1 www.komokaweather.com/komokaweather-ca
MX https://komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX https://komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX https:// komokaweather.com/cumulusmx4/index.htm
C1 www.komokaweather.com/komokaweather-ca
MX https://komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX https://komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX https:// komokaweather.com/cumulusmx4/index.htm
-
- Posts: 374
- Joined: Sun 27 Feb 2011 5:13 pm
- Weather Station: Ecowitt HP2551 & GW1100
- Operating System: Raspberry Pi OS
- Location: Kangasala, Finland
Re: Station update not working
At least I suffered from quite regular station lockups with my two old wh1080:s (without solar) until taking the sychronization in use. I have not seen any notable adverse effects with it. Both consoles are over 10 years old, so maybe the newer ones behave better regardless of the sync.mcrossley wrote: ↑Thu 30 Jun 2022 8:12 am TLDR: I don't recommend using the synchronise option on stations with solar sensors. It probably adds nothing and may be harmful on stations without solar sensors as well.
OK, there is a problem with the synchronisation code. It was written to take account of the 48 second data updates, however if you have a solar sensor it also updates at an independent 60 second period as well. This will mess up the timings completely. There is also a bug in the 48 second code that means it may fail to calculate the period accurately.
-
- Posts: 1183
- Joined: Fri 27 Jul 2012 11:29 am
- Weather Station: Chas O, Maplin N96FY, N25FR
- Operating System: rPi 3B+ with Buster (full)
Re: Station update not working
I believe that everyone will find many posts in favour of Fine Offset synchronization for Cumulus 1 users.
Equally, predominately for MX user posts, suggest better to disable synchronisation as per Mark's bug advice for both with and without solar.
- mcrossley
- Posts: 12763
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Station update not working
I have done some work on this today.
First I wanted to confirm that the 48 second update was actually 48 seconds. If we get that wrong then nothing else will work.
With CMX sampling my old WH1090 console every 0.5 seconds (as the synchronisation process does), then there was obviously a bit of jitter between each update. But after an hour the time came out at 47.9984 seconds, that is 99.997% of 48 seconds. So that value looks correct.
Next I have rewritten the synchronisation code to include a correction for the solar data - I assumed it is accurate to 1 minute as I do not have any kit to test this.
The sync code now seems reliable and does stop reading the station around the time my sensor transmits.
I looked at the code suppressing the read when the historic data block is changed. This happens on a minute, at the set logger interval. Determining this is problematic as it means the synch code would have to "hammer" the station with reads for an extended period (what if the user had 30 minute logging intervals!). There is already code in there to suppress the read of the actual data if the logging block changes, so I think I will leave as the sole avoidance mechanism for those events and see how it goes.
I've also changed the station read time from 10 seconds to 16. We will still get two reads of the data per 48 second update, but...
This means it is a divisor of the 48 second transmissions. So if we get a clash MX will shift the read timer by 8 seconds to hopefully avoid totally them from that point onwards. Also 16 is not a divisor of 60, so the reads should never stay in sync with the console logger block changes.
First I wanted to confirm that the 48 second update was actually 48 seconds. If we get that wrong then nothing else will work.
With CMX sampling my old WH1090 console every 0.5 seconds (as the synchronisation process does), then there was obviously a bit of jitter between each update. But after an hour the time came out at 47.9984 seconds, that is 99.997% of 48 seconds. So that value looks correct.
Next I have rewritten the synchronisation code to include a correction for the solar data - I assumed it is accurate to 1 minute as I do not have any kit to test this.
The sync code now seems reliable and does stop reading the station around the time my sensor transmits.
I looked at the code suppressing the read when the historic data block is changed. This happens on a minute, at the set logger interval. Determining this is problematic as it means the synch code would have to "hammer" the station with reads for an extended period (what if the user had 30 minute logging intervals!). There is already code in there to suppress the read of the actual data if the logging block changes, so I think I will leave as the sole avoidance mechanism for those events and see how it goes.
I've also changed the station read time from 10 seconds to 16. We will still get two reads of the data per 48 second update, but...
This means it is a divisor of the 48 second transmissions. So if we get a clash MX will shift the read timer by 8 seconds to hopefully avoid totally them from that point onwards. Also 16 is not a divisor of 60, so the reads should never stay in sync with the console logger block changes.