I upgraded to b3141 on 31st July. At just after 1500 BST today I restarted MX for the first time since the upgrade and noticed that the dew point values were far too low. On checking my VP2, the values shown in the console are okay, so my first fear of a misbehaving RH sensor has now gone away I use a quadratic formula to correct overreads and underreads in my VP2 humidity sensor, thanks to the ability to do this through MX's Offsets settings. My next step in tracking down the problem was to check the offset values for RH. The value for HumMult2 had been reset to 0. I found the correct value from backup copies of Cumulus.ini and manually entered it through the interface. Sure enough, the dew point values were then sensible.
Unfortunately that isn't the end of the story, as on restarting MX the HumMult2 value has reverted to 0.
On looking in Cumulus.ini there was no sign of the HumMult2 parameter. Therefore I shut down MX and manually added HumMult2 and its value.
I haven't dared to restart MX again since performing the last step! While I was in Cumulus.ini I couldn't see any other offsets ending in "2". Perhaps there's a problem in the code that rewrites Cumulus.ini?
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
Loss of HumMult2 Offset parameter after upgrade to b3141
Moderator: mcrossley
- mcrossley
- Posts: 12756
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
Good catch, yes, it reads the value correctly, but does not write it back. Adding into your Cumulus,ini should fix it for now until I can get the next release out.
-
- Posts: 2473
- Joined: Wed 08 Jun 2011 11:19 am
- Weather Station: Davis Vantage Pro 2 + Ecowitt
- Operating System: GNU/Linux Ubuntu 22.04 LXC
- Location: Alcaston, Shropshire, UK
- Contact:
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
Thanks Mark. If I have to restart will I need to pop HumMult2 back in the ini file first?
- mcrossley
- Posts: 12756
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
You shouldn't but please check. On the first run of v3.12.0 it will re-write Cumulus.ini to clean out old settings, but subsequent runs should not as it is now already cleaned up - if I coded it right!
So if you added the value back in to the Cumulus.ini created by v3.12.0 you should be OK.
So if you added the value back in to the Cumulus.ini created by v3.12.0 you should be OK.
-
- Posts: 2473
- Joined: Wed 08 Jun 2011 11:19 am
- Weather Station: Davis Vantage Pro 2 + Ecowitt
- Operating System: GNU/Linux Ubuntu 22.04 LXC
- Location: Alcaston, Shropshire, UK
- Contact:
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
Yes, it has survived a restart. I'm happy now
-
- Posts: 884
- Joined: Sat 16 Jul 2016 11:59 pm
- Weather Station: Davis VP2+ & GW1000 (Standalone)
- Operating System: Win10 Pro / rPi Buster
- Location: Australia
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
I didn't realise that Quads had been introduced; shows I've missed it in the details.
Here's a thought on the settings page though.
Rather than having the offsets & multipliers sections, what about just 3 fields of each reading.
a, b & c along with the well known "Corrected Value =ax²+bx+c"
Realistically if you are someone who'd play with the settings, you'd have a handle on the math.
Even wrap it with the warning,
Here be dragons! Only alter these settings if you understand what they do.
Cheers.
Here's a thought on the settings page though.
Rather than having the offsets & multipliers sections, what about just 3 fields of each reading.
a, b & c along with the well known "Corrected Value =ax²+bx+c"
Realistically if you are someone who'd play with the settings, you'd have a handle on the math.
Even wrap it with the warning,
Here be dragons! Only alter these settings if you understand what they do.
Cheers.
:Now: :Today/Yesterday:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
-
- Posts: 884
- Joined: Sat 16 Jul 2016 11:59 pm
- Weather Station: Davis VP2+ & GW1000 (Standalone)
- Operating System: Win10 Pro / rPi Buster
- Location: Australia
Re: Loss of HumMult2 Offset parameter after upgrade to b3141
:Now: :Today/Yesterday:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station: