The klimalogg driver tries to calculate where to start with collecting 'missed' data. This calculation will be wrong when the klimalogg memory is filled with data of different intervals. Example: the first 20.000 records have an interval of 30 minutes, then 15.000 records with an interval of 1 minute and the newer records have an interval of 5 minutes.
Also the data in the klimalogg memory can have the time stamps not in increasing order. We have seen problems with the reception of the DCF time. Then 10 march 2017 suddenly was read as 10 february 2017. One day later the time was normal again (11 march 2017 in this example). The logic in the klimalogg driver tries to overcome such timestamp jumps and will skip the records the logic thinks are bad. It might also do not foreseen actions when a number of such wrong timestamps come close next after each other. When such a situation occurs the only cure might be to clear all data in the klimalogg memory. Luc -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
