Cumulus Support

Hi,
I'm running with CumulusMX latest version, raspberry PI B+, Davis VP2 with USB datalogger

when cumulus restarts after a shutdown, it begin to record only the new data, losing the weather data when Cumulus was not running
is it normal? or maybe have I to set something somewhere?

On my previous configuration (cumulus1 windows version, and WH1081 fine offset weather station) I never missed any offline data...

different way to work? ... just to know...
thanks for your comment

Norbert

Some people seem to have this problem when there is a lot of data to download from the Davis logger at startup, but the logger doesn't send anything. I have tried to reproduce the problem, but it always works for me, no matter how much data there is to download.

Hopefully you are running the latest build, as I added some extra code which may help to at least identify the problem. If you zip up the MX diags folder and attach it, I'll have a look.

If you are running a Raspberry Pi why don't you just run it 24/7 rather that closing down and restarting.

The power consumption is minimal and it would stop any problems on restart etc.

MXdiag folder enclosed

First of all, I can see is that you don't have Cumulus set to the same logger interval as your logger, so you have the issue described in this FAQ: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

MX is correctly downloading the archive data, but there was a problem where the logger stopped sending archive data before it had all been received:

2017-02-01 15:55:04.914 Writing today.ini, LastUpdateTime = 30/01/2017 00:30:00 raindaystart = 9.4 rain counter = 9.4
2017-02-01 15:55:04.921 Log file entry written
2017-02-01 15:55:04.928 90 archive entries processed
2017-02-01 15:55:04.928 Reading archive page 18
2017-02-01 15:55:04.928 Waiting for response
2017-02-01 15:55:08.945 The station has stopped sending archive data

Cumulus has two goes at downloading archive data, and the second attempt got as far as just after midnight on the next night, when the logger stopped sending data again:

2017-02-01 15:55:42.320 Writing today.ini, LastUpdateTime = 31/01/2017 00:40:00 raindaystart = 9.4 rain counter = 9.4
2017-02-01 15:55:42.324 Log file entry written
2017-02-01 15:55:42.331 145 archive entries processed
2017-02-01 15:55:42.331 Reading archive page 29
2017-02-01 15:55:42.332 Waiting for response
2017-02-01 15:55:46.336 The station has stopped sending archive data
2017-02-01 15:55:46.354 Archive reading thread completed

I'm afraid I have no way of knowing why the logger did this. You should at least set the logger intervals to be the same.

I'll have a look at the code to see if there's anything I can do about this, but there are already multiple retries in there. As has been pointed out, one advantage of the Raspberry Pi is its low power consumption, so it costs very little to leave it running 24/7. Do you plan on closing it down for long periods?

steve wrote:I'm afraid I have no way of knowing why the logger did this.

Actually, I think it's probably because the Pi is quite slow and it takes about a minute to do the end of day rollover. The logger probably gives up waiting for the next logger entry to be read. So long as there is only one end of day rollover to do (i.e. MX was only stopped for one night) this shouldn't be a problem as MX already has two passes at doing the download. I'll see if I can think of a safe way to make it do something if the download times out like this.