Wrong data after low battery

[Vincent]

Of course the batteries became low when I was on holiday . When I loaded data to Cumulus to save information that was measured before the batteries were low I got strange results. Highest minimum temperature in records of 999,99 and dayfile looks like this: (double entries and a lot of 999's and -500's).

Code: Select all

30-04-10;9,5;338;14:20;10,6;23:10;15,0;00:00;1001,4;03:59;1008,8;16:55;7,2;00:41;4,2;12,5;226,0;6,1;14:20
01-05-10;8,2;315;07:00;8,3;23:07;13,0;18:40;1005,8;05:30;1011,5;23:00;7,2;13:20;1,5;11,1;172,9;5,1;02:20
02-05-10;11,6;45;23:22;4,1;23:44;10,8;11:58;1009,4;19:20;1011,8;02:21;7,2;20:11;9,9;8,0;191,3;7,1;22:26
03-05-10;11,9;90;13:20;4,2;00:00;7,7;17:00;1009,4;02:55;1015,6;17:30;7,2;01:08;6,0;6,1;249,7;6,5;06:25
04-05-10;7,1;360;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;1015,6;00:00;0,0;00:00;6,0;7,7;0,0;4,8;00:00
05-05-10;7,1;360;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;1015,6;00:00;0,0;00:00;6,0;7,7;0,0;4,8;00:00
06-05-10;7,1;360;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;1015,6;00:00;0,0;00:00;6,0;7,7;0,0;4,8;00:00
06-05-10;7,1;360;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;1015,6;00:00;0,0;00:00;6,0;7,7;0,0;4,8;00:00
03-05-10;7,1;360;13:40;999,0;13:40;-500,0;13:40;9999,0;13:40;1015,6;13:40;0,0;13:40;6,0;7,7;0,3;4,8;13:40
04-05-10;0,0;0;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;0,0;00:00;0,0;00:00;6,0;0,0;0,0;0,0;00:00
05-05-10;0,0;0;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;0,0;00:00;0,0;00:00;6,0;0,0;0,0;0,0;00:00
06-05-10;0,0;0;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;0,0;00:00;0,0;00:00;6,0;0,0;0,0;0,0;00:00
06-05-10;0,0;0;00:00;999,0;00:00;-500,0;00:00;9999,0;00:00;0,0;00:00;0,0;00:00;6,0;0,0;0,0;0,0;00:00
03-05-10;0,0;0;13:50;999,0;13:50;-500,0;13:50;1007,4;13:51;1007,5;13:51;0,0;13:50;6,0;0,0;0,0;0,0;13:50
04-05-10;0,0;0;00:01;999,0;00:01;-500,0;00:01;9999,0;00:01;0,0;00:01;0,0;00:01;6,0;0,0;0,0;0,0;00:01

[steve]

Presumably Cumulus was unable to make contact with the station for long periods and hence had no data for those days, so you just get the default values. I think you'll just have to edit out those entries. Presumably it's working OK again now you've replaced the batteries?

[Vincent]

Presumably Cumulus was unable to make contact with the station for long periods and hence had no data for those days, so you just get the default values. I think you'll just have to edit out those entries. Presumably it's working OK again now you've replaced the batteries?

Yes, it's working OK again now, after I edited the wrong entries, but this always happen when I change batteries so I think it's a bug with Cumulus and FineOffset stations?

[steve]

Please zip up the diags folder and attach it.

[Vincent]

Please zip up the diags folder and attach it.

OK, I hope it's useful, because this happend 5 days ago and I mentioned it today.

[steve]

Unfortunately the earliest log is from the 9th May. I suspect the problem is something to do with the state that the station memory is left in after changing the batteries, but it's hard to know exactly what the problem is without the diagnostic log. I often leave my Fine Offset station disconnected with no batteries in (I only use it for testing) and I haven't noticed a problem like this when I connect it again, there's just a gap in the data.

[Vincent]

Unfortunately the earliest log is from the 9th May. I suspect the problem is something to do with the state that the station memory is left in after changing the batteries, but it's hard to know exactly what the problem is without the diagnostic log. I often leave my Fine Offset station disconnected with no batteries in (I only use it for testing) and I haven't noticed a problem like this when I connect it again, there's just a gap in the data.

When I have it again, I will immediately zip up the diags folder and attach it!

[steve]

OK, thanks.