EasyWeather.dat

[pdw112]

Hi all,

I want to use cumulusmx with EasyWeather.dat.
But cumulusmx will not read the EasyWeather.dat file.

It's the same EasyWeather.dat file I use with Cumulus 1.

This is the file filled with data.

,2019-09-27 21:50:07,2019-09-27 21:50:07,,68,21.5,81,15.2,12.1,15.2,,1006.96,2.1,,2.5,,,WSW,,,,0.00,,,,520.07

I hope someone can help me.

Br,
Arnaut

[mcrossley]

Please zip up and post your mxdiags folder and your easyweather.dat file.

[pdw112]

hereby the mxdiag file and my easyweather.dat file

[mcrossley]

My first observation is that your easyweather.dat file is not in the correct format. It should be CSV not semi-colon separated.
At the moment I dont have access to the code that reads it in CMX, but I'd try fixing that first.

[pdw112]

Ok it's the same file that i use for cumulus 1.

[freddie]

Ok it's the same file that i use for cumulus 1.

If you compare the easyweather.dat file you posted in the first post in this thread with the easyweather.dat file from your zip file you can see the difference. In the one in the first post, the values are separated by commas. I'm assuming you got this from Cumulus 1? In the one from the zip file, the values are separated by semi-colons. Did this file come from Cumulus 1 too?

It could be due to the application you use to open the easyweather.dat file to view its contents. I'm guessing at this point, though.

You will need to find out what is changing the commas to semi-colons.

[HansR]

I don't know exactly where the easyweather.dat file comes from, but as far as I understand it, it is generated by easyweather from OffSet weather stations.

So I assume the comma separation is either a setting there or, if it is not a setting, it is probably governed by the locale. Apparently something changed there with versions of easyweather. CumulusMX however checks for a comma. Always. Most likely the easyweather software has developed in new versions.

Then there are two solutions:
1) Cumulus should not use a fixed comma to search for field separation but should use the locale (CultureInfo.CurrentCulture) to determine the separator before parsing the easyweather string (assuming both programs run on the same machine or at least both machines have the same locale)
2) Easyweather should be tricked to use the comma as separator.

I would say the first would be best on long term, by now option 2 would offer the best solution.
You could also make a small program to actually simply change all comma's before offering the file to CumulusMX.

[pdw112]

The file with the , was from cumulus 1.
The file in zip with the ; was a test.
MX don't work with the , file.
The station i use is the tfa primus.
The easyweather file created by wuhu program.

[HansR]

I presume this is the WUHU you use?
But I find no reference whatsoever to an easyweather.dat file on that site.
I have difficulty understanding what generates the easyweather.dat file.

It is not generated by Cumulus and, as far as I read the WUHU site, it is not generated by WUHU either.

A possibility I see, is that a file generated by WUHU is renamed to easyweather.dat.
And MX should work with a comma separated file, comma's or spaces separate the data (if I understand the source correctly).

[mcrossley]

Hans, that file has not been created by EasyWeather, afaik ew always uses commas and populates all the fields.

[HansR]

@MarK: Yes, I already thought so So the question is: where does it come from...

[freddie]

@MarK: Yes, I already thought so So the question is: where does it come from...

pdw112 already told you where it came from about 4 replies back. He says that commas don't work with MX so he changed commas to semi-colons as a test.

[pdw112]

Hans, that file has not been created by EasyWeather, afaik ew always uses commas and populates all the fields.

WUHU read this file:
,%[time2]time_date_international_hms%,%[time2]time_date_international_hms%,,%[humidity_levels]indoor_percent_int%,%[indoor_temperature]deg_C%,%[humidity_levels]outdoor_percent_int%,%[outdoor_temperature]deg_C%,%[dewpoint]deg_C%,%[windchill]deg_C%,,%[pressure_relative]hpa%,%[wind_speed_average]mps%,,%[wind_speed]mps%,,,%[wind_direction]name%,,,,%[rain_1h]mm%,,,,%[rain_total_tweaked]mm%

And save this as easyweather.dat
,2019-09-28 20:12:14,2019-09-28 20:12:14,,69,21.5,79,16.0,12.4,16.0,,1010.68,2.6,,3.0,,,WSW,,,,0.00,,,,521.59

when cumulusmx read this I see this fault in the mxdiag file:
Error while processing easyweather file: De index ligt buiten de matrixgrenzen.

[HansR]

@MarK: Yes, I already thought so So the question is: where does it come from...

pdw112 already told you where it came from about 4 replies back. He says that commas don't work with MX so he changed commas to semi-colons as a test.

Confusing to say the least

[mcrossley]

If you have the option set "Log extra sensors", then MX is expecting two additional fields in the .dat file - 27 and 28 for light and UV levels...

Code: Select all

     * 26*  Rain total          float   mm
     * 27*  Light reading       int     Lux
     * 28*  UV Index            int

Please check if you the "Log extra sensors" setting enabled, it doesn't look like you need it as you do not have that data in the .dat file.