Build 3257 wind speeds, rain fall & who knows what else?

[BCJKiwi]

Installed Build 3257
There are a few things that I don't understand:-
1. On the Startup screen is shows:- Opening Ecowitt extra sensors but I run a VP2 ?

2. Average wind speeds:- Previously I used the VP2 output for wind speeds, However the Average speed was stuck on 0 so I changed it to use the CMX calculated speed
Now the wind speed gauge is stuck on 16.1, the 10 min average is stuck on 42.9, the Highest Gust remains at 48.3 (which is correct).
These values also show on the MX Dashboard. and are now stuck even though I have changed back to VP2.
So, restarted CumulusMX and the average speed is now stuck on 0 and the wind sped is stuck on 12.9 for both the CMX dashboard and the website

Also the Rainfall values are less that they should be and also appear to be stuck on what appears to be from the the time build 3257 was installed.
None of these agree with the VP2 console which is varying almost constantly as we have blustery conditions.

You can see these values on https://silveracorn.nz/cumulusmx/

Any suggestions?

[freddie]

Upload your MXdiags file?

[BCJKiwi]

Have reverted to B 3248

However checked the MXdiags for the relevant period.
MXdiags shows no errors but does display the erroneous values for wind, rainfall etc as if they are the correct values.

So, no help there.

But shows irrelevant / erroneous
Creating Ecowitt extra sensors station
Checking SQLite integrity...
SQLite integrity check OK
Creating Extra Sensors - HTTP Station (Ecowitt)
Extra Sensors - HTTP Station (Ecowitt) - Waiting for data...
882 web tags initialised

Again we do not have Ecowitt, nor do we use SQLite
Davis VP2 and plain old FTP for us.

[SamiS]

Again we do not have Ecowitt, nor do we use SQLite
Davis VP2 and plain old FTP for us.

Just a clarification. If you are using CumulusMX you are using sqlite. Do not mix it with mysql that is optional.

[mcrossley]

You must have extra sensors enabled in the config: Settings | Extra Sensors | Use a second station for extra sensors

[PaulMy]

Hi Brian,
Your mention of "Opening Ecowitt extra sensors" seems that something has changed or gone wrong in your update if you have not added anything in the Extra Sensor Settings. You can if you want run as a Davis station type, and also through the Extra Sensor Settings add additional sensors, but that would take a setting change. The Extra sensors should have no affect on the Davis data. A while back I had some Ecowitt soil and air quality sensors and that worked just fine with my Davis VP2 station type.

Maybe a reinstall after making sure there is nothing in your Extra sensor settings.

Enjoy,
Paul

[mcrossley]

It would still be interesting to see a log file, preferably with debug and data logging enabled.

There are a number of people using VP2 stations using this build without any issues (including my test set-up).

[BCJKiwi]

I am mystified.

Why would I have any interest in Ecowitt when I only have a Davis VP2?

Why would I need to implement extra sensors when I don't have any?

Everything is working fine with build 3248
I update in the approved manner by applying all the files in the 3257 release over the top of 3248. This has always worked before.
I don't see any info indicating that I should be doing something else.

As I only use FTP, there are no issues with php uploads as I don't use them.

[PaulMy]

Hi Brian,
Not suggesting you need to do any Ecowitt settings whatsoever, just saying that even if Ecowitt had been selected it wouldn't make any difference in your Davis data. And only mentioned it because you indicated that you were getting Ecowitt extra sensor messages which would not be a usual thing.
I have no other thoughts on why yours is not updating correctly as I know you have done it many times in the past.

For my two CMX b3257 new version updates one is with FTP and the other PHP upload and both updated fine.

Enjoy,
Paul

[BCJKiwi]

I see Ecowitt was set in extra sensors so have turned that off.

I'm sure I never turned it on so not sure how or when that happened but it was set in b3248

[BCJKiwi]

Have tried b3257 again
Results the same as before so again reverted to b3248.

There seems to be significant differences in the contents of the data in MX diags in b3257 whwn compared to b3248.

Have attached a full MXdiags from the fresh start and also included a much smaller sample of where it seems to be going wrong by reprocessing the wind data and repeating the Current data which never changes despite the gust and speed changing.

2023-11-01 10:55:47.806 DoWind: gust=9.7, speed=9.7 - Current: gust=19.3, speed=0.0
2023-11-01 10:55:49.420 DoWind: gust=8.0, speed=9.7 - Current: gust=19.3, speed=0.0

MXDiags1.zip

MXDiags2.zip

[mcrossley]

Can you confirm the settings for:
"Calculate average wind speed" and advanced setting "Use wind speed for average calculation"
for each of these logs please

[BCJKiwi]

Well, I have reverted to b3248

I simply load the the new b3257 over b3248
I don't have calculate average wind speed set and never have:- Is this something new that needs to be set?

As I currently don't have b3257 running anywhere and I don't see any reference to Use wind speed for average calculation anywhere in b3248, I presume this is a new setting in b3257. If so I did not change it from whatever the default is in b3257.

Also I don't see any reference to Use wind speed for average calculation in the b3257 Updates.txt

[mcrossley]

I don't have calculate average wind speed set and never have:- Is this something new that needs to be set?

Many people with VP2's do enable it, if you let MX calculate the average then you will get it to 0.1 mph resolution. The VP2 is limited to integer values by the memory storage (afaik). On the newer WLL, Davis do supply the average to 0.1mph resolution.

As I currently don't have b3257 running anywhere and I don't see any reference to Use wind speed for average calculation anywhere in b3248, I presume this is a new setting in b3257. If so I did not change it from whatever the default is in b3257.

Also I don't see any reference to Use wind speed for average calculation in the b3257 Updates.txt

It's been there for years, as I said under Advanced settings in Common Options.

I'm unable to reproduce this so far with my VP2 and any combination of settings I have tried. It is strange that no one else with VP2 has reported it either - so far anyway! It's a bit of a head scratcher at the moment!

I'll continue investigating, but I may have to ask you for a sanitised version of your Cumulus.ini so that I can plug it into my test rig and see if that reproduces the problem.

[BCJKiwi]

Common Options - Current settings that are set:-
Zero Bearing
Cumulus pressure trend names
Round wind speeds
Log extra sensors
No Sensor check

Advanced Options:-
Use wind speed for average calculation NOT SET
wind average bearing & average speed times are both set to 10 which is the normal update period.

These settings have been my norm for ages.

if you let MX calculate the average then you will get it to 0.1 mph resolution

Do you mean .01?
Have had .1 kph resolution for as long as I can remember.

Cumulusini.zip

(sanitised)

Thanks