Cumulus MX, Raspberry Pi 1.2, Fineoffset WH3080

[ilteoriva]

Hello everyone,
I'm a new entry of the field of metereology, my name is Matteo.
First of all, thank you very much to Steve and to all the community for all your job.

As stated in the title, I am running CumulusMX on Raspberry Pi 1.2 (one of the first versions) and it is connected with a Excelvan (basically a Fineoffsets) WH3080. I'm using the last build (3043).
I'm experiencing a problem: the station transfers logs to CumulusMX only when it is connected.
For istance, if I connect the station at 9pm, it starts to send long to Cumulus every 10 minutes (as it is supposed to be) but it does not for all the logs that were collected previously.

On the contrary, the same setting works perfectly on a laptop with Win10: if I connect the station at 9pm, it retrives all the data of the day.

This can be a problem because if for some reasons the raspberry stops working (i.e. electricity down) I will loose all the data until the raspberry is restored.



Can someone help me?

Thank you

[steve]

Have you configured the station type correctly in Cumulus? You need the Fine Offset with solar sensors setting. If you have the correct setting, zip up the MXdiags folder and attach it, and I'll take a look.

[ilteoriva]

Hi,
the station settings are ok (Fineoffset with solar sensor).

I did some testing today: station connected from 19:47 to 21:13, then disconnected from 21:13 to 22:50, then reconnected from 22:50 to 23:50 (Bruxelles time).
As anticipated yesterday, I confirm that Cumulus takes data from the station only in the period in which it is actually connected.
No recovery of the "old" data before station connection (<19:47) and no data in the disconnection period (21:30-22:50).
Another hint that maybe can help: in the "charts", "wind chill" and "heat index" lines are not visible even if selected.

As requested, I upload the MXdiags folder

Thank you

[steve]

According to the diags files, you are closing Cumulus down, and then starting it again immediately, so there is no need for it download any logger data.

If what you are doing is disconnecting the station while Cumulus is running, Cumulus won't catch up when you reconnect the station - that's not how it works. It catches up for periods when it has been closed down.This is effectively what would happen in the situation you are concerned about - the Pi going down for some reason. You don't appear to be simulating that with your tests.

[ilteoriva]

Hello,
thank you for your answer.

What you said sounds a bit strange to me: what I did, in my "simulation", was just to turn of cumulus for about 1h to see what would happen.

Anyway, beside this, the problem is that even if the memory of the station contains data regarding the last 2 weeks, when I start CumulusMX on raspberry and connect the station, it does not download those data from the station to cumulus (conversely, on win10 it does).
Cumulus starts download data only when it is running and the station is connected.
Again, I do not understand why on the temperature chart "wind chill"and "heat index" are not functioning: I select them but no lines are displayed on the chart (again, on win10 everything ok).

Is that possible that all this is because of how I did the installation?
This was my procedure:

On my laptop
download CumulusMX 3042 and unzip
download CumulusMX_2.5.3.1.zip at the end of this page: https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13767
Unzip and copy the content of the zip file into CumulusMX folder

On raspberry
Command line
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install screen
sudo apt-get install mono-complete
Then, via file manager, copy the CumulusMX folder on raspberry (cumulus files in home/pi/CumulusMX)\
Command line again
sudo chmod +x /home/pi/cumulusmx.sh
and to start cumulus
sudo /home/pi/cumulusmx.sh to start cumulus

Is that possible that this procedure (or the script in the zip files) leads to a "partial" startup of cumulus and therefore it is not 100% working?


Thanks

[steve]

I suggest that you don't use the script (as good as it is) until you have resolved the issues you are having, as this is just adding extra complication. It appears thar MX is not being closed properly, which is why what you say you are doing is not reflected in the doags file.

Regarding heat index and wind chill graphs not appearing - what values are shown in the dashboard? Are your temperature and wind figures within the default ranges for heat index and wind chill to be different from the ambient temperature? I can't remember the exact details, they are in the wiki and/or FAQ (for wind chill, the temperature has to be below 10C, for example).