Wrong visualization after editing dayfile.txt

[Piero]

Hello,
I modified the dayfile.txt with the internal editor, adding two dates using the "create missing".
After adding the date 01/05/2013 I pressed "ok", without any problem.
After entering the date 02/05/2013, I again pressed "ok", and again no problem.
Then I rebooted cumulus and, opening the editor, the dayfile.txt is shown as attached.
The log of Cumulus displays no error, it seems that everything runs smoothly.
What should I do?

thanks

Piero

[steve]

It looks like the editor has got confused over the list and decimal separators on your system, and made a bit of a mess of your file. Could you zip up the diags folder and attach it, please?

I suggest that you stop Cumulus and find the dayfile.txt from before you used the editor, from the backup folder (a copy is taken each night and each time you start Cumulus, so there should be one from just after midnight last night) and use that until I can work out what the problem is. Could you let me have a copy of that dayfile.txt as well, please.

[Piero]

Thanks Steve,
now I'm not at home, but later I'll send you the files.

A question: I use a Davis cabled Weather Envoy manufactured in 2010 (#6316CEU). Weatherlink sees it as vantage pro. Is this the correct setting or should select "vantage pro 2"?
I ask this because I would not that this was the cause of the incorrect file writing/reading.

Piero

[steve]

You need to use the Vantage Pro2 setting in Cumulus. That wouldn't be the cause of the problem with dayfile.txt, it's definitely something to do with your regional settings; somewhere they are being confused.

Using the wrong setting might be why you have those two days missing, though; it might not have been able to read all of the data from the logger.

[Piero]

Hi Steve,
here attached the files you asked me.

Piero

[steve]

It looks like the grid in the editor doesn't use your settings correctly when it's saving the file. I'll investigate and see if I can work out what I need to do to make it work properly; it probably needs to be told what settings to use, where I expected it to use the system settings automatically.

[Piero]

Ok Steve, thanks.
Do you think I could re-install cumulus deleting everything? With the correct settings "Vantage Pro2" and "use datalogger" activated cumulus should rebuild all the archives up to about 3 months ago (the capacity of the datalogger), right?

[steve]

If you delete everything, it won't download the 'old' data from the logger when you start it again, you'll need to have a today.ini file with an old timestamp in it - see http://wiki.sandaysoft.com/a/FAQ#I.E2.8 ... er_station

[steve]

I've just tried to reproduce your problem using your settings, and it all works fine. Have you been editing dayfile.txt with something else, perhaps?

[Piero]

no, I only used the editor of cumulus.
I also noticed that, editing the alltime records, the hours are in the hh.mm format but, when you click to open the single cell, they turn into hh:mm format. The change is successful but, again opening the editor window, I find the time in the hh.mm again, with the correct value. What do you think?

[steve]

I also noticed that, editing the alltime records, the hours are in the hh.mm format but, when you click to open the single cell, they turn into hh:mm format. The change is successful but, again opening the editor window, I find the time in the hh.mm again, with the correct value. What do you think?

I don't know why it does that, but as long as the result is correct, that's the important thing.

[Piero]

Well. So what do I do then with my dayfile.txt?

[steve]

Well. If the editor doesn't work for you for some reason that I can't explain, then you'll have to just use the one that is OK. You could perhaps use the editor to fetch the values and then edit the file manually.

I'm not sure that you can actually create the correct missing entries anyway, as you clearly have data missing. I noticed this:

08/05/2013 15.27.37.089 . VP2: Downloading history from 08/05/2013 15.00.00
08/05/2013 15.27.37.089 . y=2013 m=5 d=8 h=15 m=0
08/05/2013 15.27.43.370 . VP2: DownloadData_V = 2
08/05/2013 15.27.43.370 . VP2: GetNumberOfArchiveRecords_V = 2
08/05/2013 15.27.43.370 . VP2: Number of history records = 2
08/05/2013 15.27.43.370 . Logger entry zero: Y = 2013, M = 3, D = 16, H = 5, M = 30
08/05/2013 15.27.43.370 . VP2: Earliest timestamp 16/03/2013 5.30.00
08/05/2013 15.27.43.370 . VP2: Earliest timestamp is earlier than requested
08/05/2013 15.27.43.370 . VP2: Find first entry after 08/05/2013 15.00.00
08/05/2013 15.27.43.370 . VP2: Checking logger entry 0 Y = 2013, M = 3, D = 16 H = 5, M = 30
08/05/2013 15.27.43.370 . VP2: New earliest timestamp 16/03/2013 5.30.00
08/05/2013 15.27.43.370 . VP2: Checking logger entry 1 Y = 2013, M = 3, D = 16 H = 6, M = 0
08/05/2013 15.27.43.370 . VP2: New earliest timestamp 16/03/2013 6.00.00
08/05/2013 15.27.43.370 . VP2: No history records to process

So your logger is saying it only has two entries in it, and they are both from 16th March. So it looks like your logger isn't working correctly.

[Piero]

I would not know what to say. Cumulus is working with VVP, it could be a problem of VVP. But VWS, that I used before, is continuing to regularly save dataso I think the data logger functions. I will try to erase everything and reinstall Cumulus, then I will attach again the folder "diag" for a check, if I can.

Thanks anyway for your support

[steve]

Cumulus is working with VVP

That's useful information. There are known problems with VVP and the Davis DLL which Cumulus uses; there is a warning about this in the readme.txt. There are particular problems with reading logger data.