Transition from DST

[XBower]

Hi.

This morning, we went from Daylight Saving Time to Normal time.
I notices a strange thing in my log after that.
The transition at 0300 went OK, as far as I can see:
27-10-13;01:30;12,6;97;12,1;0,4;4,0;314;0,0;0,4;999,02;493,2;23,6;44;4,0;12,6;12,6;0,0;0;0,00;0,00;13,0;0;0,0;315;0,0;0,4
27-10-13;01:40;12,6;97;12,1;0,4;4,0;156;0,0;0,4;998,92;493,2;23,6;44;4,0;12,6;12,6;0,0;0;0,00;0,00;13,0;0;0,0;157;0,0;0,4
27-10-13;01:50;12,6;97;12,1;0,9;3,1;156;0,0;0,4;998,89;493,2;23,6;44;3,1;12,6;12,6;0,0;0;0,00;0,00;12,7;0;0,0;157;0,0;0,4
27-10-13;01:50;12,7;97;12,2;0,4;3,1;156;0,0;0,4;998,68;493,2;23,4;44;2,7;12,7;12,7;0,0;0;0,00;0,00;13,0;0;0,0;157;0,0;0,4
27-10-13;02:00;12,7;96;12,0;0,4;3,1;314;0,0;0,4;998,62;493,2;23,4;44;3,1;12,7;12,7;0,0;0;0,00;0,00;13,0;0;0,0;315;0,0;0,4
27-10-13;02:10;12,7;96;12,0;0,4;2,2;156;0,0;0,4;998,58;493,2;23,4;44;2,2;12,7;12,7;0,0;0;0,00;0,00;13,0;0;0,0;157;0,0;0,4

But I wonder a bit what might have happened when I fired up my system this morning, I had my system shut down during the night.
I miss 1.5 hour of data:
27-10-13;12:20;13,9;88;11,9;0,9;4,0;156;0,0;0,6;991,61;493,4;23,2;45;4,0;13,9;13,9;0,0;0;0,00;0,00;13,9;231;0,0;157;0,0;0,6
27-10-13;12:30;13,9;88;11,9;1,3;4,9;156;0,0;0,6;991,37;493,4;23,3;45;4,9;13,9;13,9;0,0;0;0,00;0,00;13,5;228;0,0;157;0,0;0,6
27-10-13;12:40;14,0;87;11,9;1,3;6,3;292;0,0;0,6;991,17;493,4;23,3;45;6,3;14,0;14,0;0,0;0;0,00;0,00;13,6;223;0,0;292;0,0;0,6
27-10-13;14:20;13,7;88;11,7;0,9;3,6;204;0,0;0,8;989,34;493,6;23,7;44;1,3;13,7;13,7;0,0;0;0,00;0,00;13,6;124;0,0;212;0,0;0,8

I can't see the reason for this.
Is there any?

I also enclose the diag files.

Regards

[steve]

The station didn't send the data for that period. When Cumulus asked for the data it needed to catch up when it started at 14:10, the station only sent data up to 12:40. Is the clock correct on the console? It looks like the console clock did go back an hour, but from 02:00 to 01:00. Perhaps it then got confused about how many logger entries were actually available.

[XBower]

The station didn't send the data for that period. When Cumulus asked for the data it needed to catch up when it started at 14:10, the station only sent data up to 12:40. Is the clock correct on the console? It looks like the console clock did go back an hour, but from 02:00 to 01:00. Perhaps it then got confused about how many logger entries were actually available.

Hi.
Yes, the clock on the console is OK, and it was before I fired up the system, I doublechecked that.
But if it went back from 02:00 to 01:00 as You say (for whatever reason), there's no wonder there is a confusion about what is what.
It does not matter vary much that this data is gone, I was merely wondering about the reason for it.

Has perhaps anybody else seen this effect on the Vantage Vue station, with IP logger?

Thanks

[steve]

I have a VP2 and serial logger, and I run Cumulus overnight (so the effect for me was an hour of apparently duplicated data), but I can back up my data and 'rewind' to midnight to see what it would have done. There are often queries about DST beginning and ending and what happens, but I don't remember anyone ever seeing this before.

[steve]

The same thing happened with my test. I reset my last download time to just after midnight, and started Cumulus at 14:25. The station only sent data to 13:10.

So it's either an issue that affects all Davis stations, or (perhaps more likely) it's a bug in the Davis DLL which Cumulus uses.

[XBower]

The same thing happened with my test. I reset my last download time to just after midnight, and started Cumulus at 14:25. The station only sent data to 13:10.

So it's either an issue that affects all Davis stations, or (perhaps more likely) it's a bug in the Davis DLL which Cumulus uses.

Hi.

Interesting...
Thanks a lot for Your help.
Well, I see nothing suspect in the uploads to Weatherlink.com, so the DLL seems to be the best bet.
This one has shown to be far from bug free.

Regards