Page 1 of 1

Realtime.txt not updated

Posted: Sun 19 Jul 2009 3:59 pm
by scala49
Hello to all,
I am a new user and I apologize if I do not write English well. I use a short time the software cumulus and I find it very well done. Only that I'm having the same problems. When FTP is not working due to temporary interruption of the DSL line, the program does not update the most realtime.txt. I ask kindly if you could solve this problem. At the time I use the WMR968 station, but in a few days get the model WF1080.
Hello and thank you.
NB: as soon as possible send a donation.
> inverti

Re: Realtime.txt not updated

Posted: Sun 19 Jul 2009 5:34 pm
by steve
Do you mean that when your internet connection comes back again, Cumulus doesn't start uploading the realtime.txt file again?

[Moved to separate topic; duplicate posts deleted]

Re: Realtime.txt not updated

Posted: Sun 19 Jul 2009 10:38 pm
by scala49
Tanks
in practice it is so ...
the software tells me that he had a problem and asks me to close, ignore, or restart.
In the meantime, continues to record and send data via FTP (when the ADSL line back to work) and the graphs updated htm files but can not update the file on your local PC realtime.txt

Re: Realtime.txt not updated

Posted: Sun 19 Jul 2009 11:38 pm
by steve
scala49 wrote:the software tells me that he had a problem and asks me to close, ignore, or restart.
When Cumulus 'crashes', which it sounds like you are describing, it normally offers you the option to save a bug report, which is a file called bugreport.txt. If it's doing that, could you please attach the bugreport.txt file so I can have a look at it and see what the problem is? If it's not doing that, could you attach a screen shot of the error message?

Re: Realtime.txt not updated

Posted: Mon 20 Jul 2009 8:24 am
by scala49
yes, this is the file

Re: Realtime.txt not updated

Posted: Mon 20 Jul 2009 8:47 am
by steve
Sorry, I didn't realise when I moved your post that when you said you had the same problem, you meant the moon.bmp problem. As there was already a fix for that, I thought it must be a different problem. This was fixed (by trapping and ignoring the error) in the first 1.8.8 beta: https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=1132