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
Search found 44 matches
- Thu 04 Apr 2024 4:06 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Beta Build 4019
- Replies: 29
- Views: 1224
Re: Beta Build 4019
4019 running just fine here. Weather station: Davis Vantage Pro2 System: Raspberry Pi 4 Model B Rev 1.5 OS: Linux 6.1.21-v8+ aarch64 Description: Debian GNU/Linux 11 (bullseye) Microsoft.NETCore.App 8.0.3 Memory info: total used free shared buff/cache available Mem: 3794 521 435 100 2837 3096 Swap: ...
- Wed 03 Apr 2024 7:21 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: CumulusMX V4 beta - WU not updating
- Replies: 5
- Views: 217
Re: CumulusMX V4 beta - WU not updating
Rapid fire disabled
Harm
Harm
- Mon 01 Apr 2024 9:08 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: CMXv4 upgrade with no issues
- Replies: 3
- Views: 156
Re: CMXv4 upgrade with no issues
Also upgraded to CMX V4 build 4018 + CUtils V7.0.0 with no issues.
@MarK and Hans
Harm
@MarK and Hans
Harm
- Fri 10 Nov 2023 8:13 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Parse error Latest error
- Replies: 3
- Views: 287
Re: Parse error Latest error
Error solved with double quotes.
Thanx again.
Harm
Thanx again.
Harm
- Thu 09 Nov 2023 6:56 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Parse error Latest error
- Replies: 3
- Views: 287
Re: Parse error Latest error
Thanks for the solution, if will try and wait for the real solution i wait.
Harm
Harm
- Thu 09 Nov 2023 10:30 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Parse error Latest error
- Replies: 3
- Views: 287
Parse error Latest error
Lately I've been getting the following message on some of my website pages: Parse error: syntax error, unexpected identifier "System" in /home/deb61496/domains/weerstationtzandt.nl/public_html/wt_data_inc.php on line 534 This is caused by the web tag //-- Section OTHERS -- $LatestError = '...
- Fri 12 May 2023 12:48 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: **** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
- Replies: 2
- Views: 212
Re: **** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
ok thanks and i will wait
Harm
Harm
- Wed 10 May 2023 4:28 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: **** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
- Replies: 2
- Views: 212
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
I get the message in the service console:
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Here are the zipped MXdiags
Harm
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Here are the zipped MXdiags
Harm
- Thu 16 Mar 2023 5:40 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Several PHP errors
- Replies: 2
- Views: 164
Re: Several PHP errors
thanks and i can live with it.
- Thu 16 Mar 2023 4:37 pm
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Several PHP errors
- Replies: 2
- Views: 164
Several PHP errors
I have several PHP errors in the MXDiag file.
All (PHP) uploads are going well. But I can't explain the errors or find a solution for them.
Latest version CMX , moved to PHP with $limitPath = false;
Harm
All (PHP) uploads are going well. But I can't explain the errors or find a solution for them.
Latest version CMX , moved to PHP with $limitPath = false;
Harm
- Sun 09 May 2021 9:39 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Error sending Test Email
- Replies: 10
- Views: 1233
Re: Error sending Test Email
ok thanks and no hurry Mark.
Harm
Harm
- Sun 09 May 2021 8:36 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: Error sending Test Email
- Replies: 10
- Views: 1233
Re: Error sending Test Email
after upgrade to build 3130 i still need to switch on email logging.
Harm
Harm
- Mon 03 May 2021 9:58 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: No non-realtime ftp if the log file is too large.
- Replies: 9
- Views: 958
Re: No non-realtime ftp if the log file is too large.
The last rollover went normally with a size of 20,520 kb and the uploads continued as usual.
So I cannot reproduce the "error".
I will keep an eye on the progress.
But it remains a strange phenomenon why the realtime FTP just continued and the 10 min FTP stopped.
Harm
So I cannot reproduce the "error".
I will keep an eye on the progress.
But it remains a strange phenomenon why the realtime FTP just continued and the 10 min FTP stopped.
Harm
- Sun 02 May 2021 10:20 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: No non-realtime ftp if the log file is too large.
- Replies: 9
- Views: 958
Re: No non-realtime ftp if the log file is too large.
@Freddie
No change of permissions and CMX runs as administrator
Harm
No change of permissions and CMX runs as administrator
Harm
- Sun 02 May 2021 9:47 am
- Forum: Cumulus MX Current (releases since b3043)
- Topic: No non-realtime ftp if the log file is too large.
- Replies: 9
- Views: 958
Re: No non-realtime ftp if the log file is too large.
@Mark
There were 11 created missing log files with a date younger than the log file in the MXdiags directory.
Harm
There were 11 created missing log files with a date younger than the log file in the MXdiags directory.
Harm