Wrong visualization after editing dayfile.txt

[Piero]

I have read the readme.txt and I apologize for not having done it before. I reinstalled Cumulus, I added the line VP2SleepInterval = 1100 to the [Station] section of cumulus.ini, but there continues to be something that does not work in the records file.
This time I did not touch the dayfile.txt but I only changed the alltime records. Everything seemed ok, but when I restart Cumulus yesterday's rain (and therefore also the monthly and annual) were increased to 73.9 mm. I then tried restarting several times but it is no longer happened. Then I tried to change another alltime record and, at the next reboot, again an increase of 73.9 mm of rain, and some alltime records were changed without any mine modify.
It seems that there is a problem in managing data files, as if some data were altered or corrupted by saving the changes. Sorry Steve, I tried to describe the problem as well as possible.

[steve]

Please zip up the diags folder and attach it, together with the alltime.ini file and the alltimelog.txt file. Please indicate which all-time records were changed unexpectedly.

[Piero]

I did other tests: it seems that these 73.9 mm of rain on startup are not dependent on changes in the alltime records, but from some other error. I closed and restarted several times without doing any operation or modification intermediate: sometimes cumulus opens with 73.9 mm of dailyrain and hourlyrain, sometimes these values ​​are 0. Obviously, however, this value of 73.9 is saved in alltime record and monthly records.
After reinstalling seemed that the problem had disappeared but a little while ago, after about 11 hours of work, has come back.
The values ​​that were changed unexpectedly before the reinstall were the time of maximum and minimum humidity.
I attach the files that you asked me, the operating system is win xp sp3.
VVP did not give any error and VWS and Weatherlink continue to operate normally.
Thank you very much

[steve]

It's getting inconsistent rain figures from VVP (the figure is supposed to be the annual rain total from the console):

11/05/2013 04.22.40.812 . VP2: Setting raintotal from current station value: 273,799987792969

11/05/2013 14.38.54.640 . VP2: Setting raintotal from current station value: 347,726013183594

11/05/2013 14.41.40.734 . VP2: Setting raintotal from current station value: 273,799987792969

11/05/2013 14.42.53.593 . VP2: Setting raintotal from current station value: 347,726013183594

11/05/2013 14.43.46.062 . VP2: Setting raintotal from current station value: 347,726013183594

11/05/2013 14.44.38.875 . VP2: Setting raintotal from current station value: 273,799987792969

This is why Cumulus is showing strange rain totals, which keep changing. I can't see anything wrong anywhere else, except that it looks like you have deleted all of your old data, but alltime.ini shows dates from before today? But it's not clear to me exactly what you've done.

Apart from the VVP issue, one thing I would suggest is that you reset your regional settings in Windows, Change the format settings to some other location (and save the change) then change them back to Italian. Don't do this while you have any software running.

There was an issue of saving the rain counter read from the station when Cumulus was stopped and started a lot over a short period of time, as you've been doing. That doesn't account for the values coming back from VVP, but you should probably install 1.9.4 to make sure you don't hit that problem, which will confuse things even more.

[Piero]

Sorry for the password, did not I think.
In practice I have removed entirely cumulus using the uninstall and deleting the folders. I reinstalled Cumulus and, once started, I have included the value of total rain to the master configuration, and then I corrected manually inserting records alltime those recorded so far by VWS, which has started running a long time ago, one of my goals is that Cumulus manages the web page that lists the highs recorded, because VWS not have this function. That's why you are getting alltime records older than the date of entry into operation of cumulus, are the ones I entered manually.
So you advise me to reset the regional settings and install the 1.9.4 beta?

[steve]

So you advise me to reset the regional settings and install the 1.9.4 beta?

Yes, the regional settings because of that problem you had previously with dayfile.txt becoming corrupted; I still don't know what caused that as I am unable to reproduce it, and I am not aware of anyone else having the problem. And 1.9.4 because if you start and stop Cumulus as you have been doing, it is possible that you will hit the problem in 1.9.3 with the rain figure not being stored, which will only confuse things as you already have the rain total problem from VVP.

[Piero]

Ok, I'll do as you're said, then soon I'll let you know.

Thanks a lot for your quick answers and best regards

[Piero]

Here we are.
I deleted everything and installed the 1.9.4, making her start directly connected to the data logger and not VVP. I waited a few minutes, then I modified with the internal editor the alltime records. After a few more minutes I closed Cumulus and I rebooted, changed alltime records were still there, the rain was ok, so I changed the connection settings, I closed, I modified the cumulus.ini for VVP and I rebooted with VVP. All fine. It was just before midnight.
This morning I found all the alltime records that I had changed, except for one really increased in the night and except the values ​​of dew point, arbitrarily canceled and rewritten by the program. Now I again corrected the values ​​of dew point and everything seems to work well, let's see what will happen after midnight. Meanwhile, I am attaching the file where you should find what I told you.
There is also a screenshot where you can see a problem in the visualization of barometer's trend.

[steve]

except the values ​​of dew point, arbitrarily canceled and rewritten by the program.

There's no indication in the logs of the dew point record changing. These are the current values, are they incorrect?

highdewpointvalue=22,8999996185303
highdewpointtime=21/08/2012 18.12.00
lowdewpointvalue=-18
lowdewpointtime=15/03/2013 15.44.00

What did they change from? What did they change to? What is the other one that you say changed?

let's see what will happen after midnight

Unless you give me specifics, it's almost impossible to say what's going on.

Meanwhile, I am attaching the file where you should find what I told you.

There is no indication of any problem that I can see in the logs. But unless I know what I'm looking for, I may have missed something. You may well have found a bug in Cumulus for all I know, but if you have, it's a very strange bug that it somehow rewrites the all-time records without going through the code which updates the all-time records and logs the change, and it's a bug that apparently no-one else has seen. I note that you have changed the default install location against recommendation, and put it in 'program files', which is know to cause problems.

There is also a screenshot where you can see a problem in the visualization of barometer's trend.

What is your display size? Screens of less than 1024x768 are not supported. I have tried to make Cumulus resize itself on small screens, but there are limits to what I can do. You can use the option to turn off the barometer trend text if you wish.

[Piero]

There's no indication in the logs of the dew point record changing. These are the current values, are they incorrect?

highdewpointvalue=22,8999996185303
highdewpointtime=21/08/2012 18.12.00
lowdewpointvalue=-18
lowdewpointtime=15/03/2013 15.44.00

What did they change from? What did they change to? What is the other one that you say changed?

I entered these values ​​during the first start (among other things, the maximum entered value was 22.9 and now I see 22.8999996185303) and checked that they were saved by closing and restarting cumulus. But the next morning, the values ​​of maximum and minimum, with date and time, were those recorded in the night, as if I did not ever changed. In fact, you confirm that there were no initial changes in the log of those values​​. The values ​​that you have reported are the ones I reintroduced the next morning, when I noticed that they had not been stored.

let's see what will happen after midnight

Unless you give me specifics, it's almost impossible to say what's going on.

I wanted to see what was going on after midnight, because I thought it might be a problem that occurred at the change of the day. However, this time no record has been changed, everything seems to work regularly.

and it's a bug that apparently no-one else has seen. I note that you have changed the default install location against recommendation, and put it in 'program files', which is know to cause problems.

Reading the readme.txt file I understood that the problem of the installation directory concerned only win7, then maybe the problem is due to that. Ok for the barometer.

Sorry, I know I'm wasting your time but things went really so.

[steve]

among other things, the maximum entered value was 22.9 and now I see 22.8999996185303

They are the same number, it's just the way they are stored internally.

Reading the readme.txt file I understood that the problem of the installation directory concerned only win7

I believe that some changes were done in XP SP3 which means that problems can occur with that, with programs like Cumulus which are in Program Files but break the rules and write to their own directory.

[Piero]

well, after 3 additional days of continuous work everything seems to work properly .. I have also tried to close and restart but this time no record has been changed.
Mysteries ... or luck. If some saving error will reoccur this time I'll try to install it in c:\cumulus.
Thanks anyway Steve for your support, good work

Piero

[Piero]

After more than 20 days of work, today I opened the data log viewer and I saw the attached image. Throughout this period cumulus worked without ever being restarted and I did not do updates pc or similar actions. I just changed the alltime record immediately after installation, but in the following days, all logs were displayed correctly. I have not exactly figured out on which day is the change occurred.

[steve]

Could you attach the May log file, please?

[Piero]

Of course.
Please note that the display error only occurs loading the dayfile.txt, alltimelog and may13log have no problems.