Catch Up worked and now it doesn't...

[agsteele]

A week or so back I upgraded Cumulus to v1.9.2 build 992. It was a clean installation and all worked well and I suddenly enjoyed the Catch Up function with my WS2300 weather station and Weather Underground and the Met Office WOW service.

Most days I shutdown my PC overnight so the first thing each morning Cumulus did its catch up stuff.

After three days or so I got an error light and the error states "Actual Date & Time : Unable to read archive data"

Since when this has happened every morning. Yesterday I upgraded to build 1001 but this makes no difference to the issue.

I noted another thread which suggested that I might disable the 'Update display during logger download' but this mad no difference either.

Since the charts and graphs in Cumulus are not showing any overnight data I guess the issue is with downloading the overnight data from the WS2300 rather than the Catch Up upload.

Can anyone suggest anything to kick the process back into life?

Thanks.

Andrew

[steve]

Since the charts and graphs in Cumulus are not showing any overnight data I guess the issue is with downloading the overnight data from the WS2300 rather than the Catch Up upload.

Yes, that's right. If you zip up the diags folder and attach it, I might be able to spot something, but I suspect I won't be able to say any more than we know already - it can't download the data from the logger. All it does to get the archive is read a particular area of the station's memory, so in that respect it's just the same as reading 'live' data. So it's not obvious to me what the solution might be, I'm afraid. Hopefully someone with a La Crosse station will be able to suggest something.

[agsteele]

The data directory is attached...

But an update too... I just installed build 1002 and noticed that on 25 June I had a low temperature recording of -29.6C (and similarly low dew points etc). I'm not sure how that was achieved but clearly it was wrong. So I've removed all the data for 25 June from the various data files and when I launched the new version of Cumulus I got a brief flash of the catch up lamp and no errors reported.

So, could the aberration in the data recorded have been the cause? Coulod the new build have fixed something? We'll see. I'll report back after a short time with Cumulus turned off to see what happens when I restart with archive data to recover.

Andrew

[steve]

So, could the aberration in the data recorded have been the cause? Coulod the new build have fixed something?

Almost certainly not. And looking through the diags files, I can see lots of '-1000' errors while reading live data, which is my error code for 'couldn't read the station's memory', so Cumulus is clearly struggling to read the data from your station quite often, not just when reading the logger data.

How is your station connected to your PC?

[agsteele]

And looking through the diags files, I can see lots of '-1000' errors while reading live data, which is my error code for 'couldn't read the station's memory', so Cumulus is clearly struggling to read the data from your station quite often, not just when reading the logger data.

How is your station connected to your PC?

I just restarted Cumulus after an hour or so shutdown and the catch up worked fine and no errors again.

The WS2300 has a serial-USB comm port device connected and that slots into a USB port on my laptop's docking station configured to be COM11:

Andrew

[steve]

The WS2300 has a serial-USB comm port device

This is the most likely cause of the problem. Some Cumulus users get reasonable results using one of these, others not very good results at all. Some serial/USB converters seem to be worse than others. But I'm afraid that if you have to use one of these with Cumulus, I can't offer any support.