Cumulus Support

Hi,

1) After modifications made when I click on [Web Update] in Cumulus main screen, I often see a shift of the entire screen and on top it shows: Cumulus (not responding).
Within 5 -10 seconds it shifts back to original position and it actually does the ftp update.
Any explanation for this phenomena?

2) To all with a WMR200A: Don't do a PC or Cumulus reset between midnight and 01:00am.
I've forgotten this a few times, and ran into problems with Dayfile.txt or Yesterday display on Cumulus main screen (many values returned to 0.0). Data totally messed up.
Any solutions for this, Steve?

Thanks,

Arthur

avoorpool wrote:1) After modifications made when I click on [Web Update] in Cumulus main screen, I often see a shift of the entire screen and on top it shows: Cumulus (not responding).
Within 5 -10 seconds it shifts back to original position and it actually does the ftp update.
Any explanation for this phenomena?

No, sorry, no idea. I've never seen that happen and I can't explain it. I'll switch my test machine over to the WMR200 and see if I can reproduce it; it might be specific to running with that type of station.

2) To all with a WMR200A: Don't do a PC or Cumulus reset between midnight and 01:00am.
I've forgotten this a few times, and ran into problems with Dayfile.txt or Yesterday display on Cumulus main screen (many values returned to 0.0). Data totally messed up.
Any solutions for this, Steve?

In the beta version that I uploaded and announced yesterday, hopefully.

Hi Steve,

Thanks. Is the current beta version stable enough to replace Cumulus 1.9.2 (1032) ?

Arthur

avoorpool wrote:Is the current beta version stable enough to replace Cumulus 1.9.2 (1032) ?

It seems to be; no-one is reporting any serious problems.

steve wrote:I'll switch my test machine over to the WMR200 and see if I can reproduce it

I've tried that and had no problems. For a web update, it processes the files on the main thread, before switching to a background thread to do the ftp. I wonder if your files take a very long time to process for some reason, which would lock up the UI and cause the 'not responding' message.