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

Planning Upgrade Cumulux MX 3.18 b3190 - tips

From Cumulus MX version 3 build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since, and has recently released Cumulus MX version 4. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
penzio
Posts: 7
Joined: Tue 28 Jun 2022 8:02 pm
Weather Station: OneConcept
Operating System: Debian - Raspberry
Location: Italy- Trentino Alto Adige

Planning Upgrade Cumulux MX 3.18 b3190 - tips

Post by penzio »

Hi everybody.
I use Cumulus MX 3.18 b3190 on a Raspberry with Mono.
In this Christmas holiday i would like to upgrade Cumulus. I think this is now necessary (?!)
Can you tell me te major steps from my version to the last? For details i will search in the forum topics or eventually ask you some help. :oops:


Thank you,

Lorenzo
water01
Posts: 3669
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: Planning Upgrade Cumulux MX 3.18 b3190 - tips

Post by water01 »

David
Image
penzio
Posts: 7
Joined: Tue 28 Jun 2022 8:02 pm
Weather Station: OneConcept
Operating System: Debian - Raspberry
Location: Italy- Trentino Alto Adige

Re: Planning Upgrade Cumulux MX 3.18 b3190 - tips

Post by penzio »

Thank you! :oops:
Post Reply