WeatherDuino Forum

Full Version: Random date changes
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7
Just updated and still getting issues here too

SDK version:2.0.0(5a875ba)
Farylink Technology Co., Ltd. v1.0.0.2
May 11 2017 22:23:58
OK
RTC current date: Jun 05 2018
RTC current time: 11:50:36
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 22:50:37
RTC adjusted to local time: 11:50:37
RTC current date: Jun 05 2018
RTC current time: 11:50:36

Got an odd date first start now showing correct date but will watch it. RTC is definitely out of whack with Jun 5th
As an aside I think this problem may also be upsetting the Davis/Vantage data output, I've been trying to get my station going with Weewx but there are some issues with the date being sent with the data. I suspect it's related?? Here is a data capture -- note that the first REC data blocks have a date of 2019-09-11 (And are NZST - should be NZDT), whereas the LOOP packets have the correct date

Code:
REC:    2019-09-11 12:05:00 NZST (1568160300) appTemp: 23.7946336801, barometer: 996.241532442, cloudbase: 1192.83426336, consBatteryVoltage: None, dateTime: 1568160300, dewpoint: 13.2578694156, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 22.7777777778, highRadiation: 8.0, highUV: 0.0, humidex: 25.7175378458, inDewpoint: 12.5050008741, inHumidity: 48.0, inTemp: 24.2222222222, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 677.517690702, outHumidity: 55.0, outTemp: 22.7777777778, radiation: 5.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 22.7777777778, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
REC:    2019-09-11 12:10:00 NZST (1568160600) appTemp: 23.9395702779, barometer: 996.106076916, cloudbase: 1193.82866351, consBatteryVoltage: None, dateTime: 1568160600, dewpoint: 13.3610055859, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 22.8888888889, highRadiation: 6.0, highUV: 0.0, humidex: 25.8866899091, inDewpoint: 12.3022086734, inHumidity: 48.0, inTemp: 24.0, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 678.470118882, outHumidity: 55.0, outTemp: 22.8888888889, radiation: 6.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 22.8888888889, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
REC:    2019-09-11 12:15:00 NZST (1568160900) appTemp: 23.8477397072, barometer: 996.139940797, cloudbase: 1228.9199514, consBatteryVoltage: None, dateTime: 1568160900, dewpoint: 13.0795786931, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 22.8888888889, highRadiation: 9.0, highUV: 0.0, humidex: 25.7291442751, inDewpoint: 11.9820744371, inHumidity: 47.0, inTemp: 24.0, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 678.963138624, outHumidity: 54.0, outTemp: 22.8888888889, radiation: 9.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 22.8888888889, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
REC:    2019-09-11 12:20:00 NZST (1568161200) appTemp: 25.0073116388, barometer: 996.207668561, cloudbase: 1348.87628346, consBatteryVoltage: None, dateTime: 1568161200, dewpoint: 13.22865792, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 24.0, highRadiation: 17.0, highUV: 0.0, humidex: 26.9233851327, inDewpoint: 12.2008068001, inHumidity: 48.0, inTemp: 23.8888888889, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 678.996340225, outHumidity: 51.0, outTemp: 24.0, radiation: 10.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 24.0, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
REC:    2019-09-11 12:25:00 NZST (1568161500) appTemp: 25.1971216855, barometer: 995.97062139, cloudbase: 1389.00049386, consBatteryVoltage: None, dateTime: 1568161500, dewpoint: 13.1290899619, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 24.2222222222, highRadiation: 12.0, highUV: 0.0, humidex: 27.090004937, inDewpoint: 12.0486967731, inHumidity: 48.0, inTemp: 23.7222222222, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 678.570029189, outHumidity: 50.0, outTemp: 24.2222222222, radiation: 9.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 24.2222222222, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
LOOP:   2018-10-30 12:13:45 NZDT (1540854825) altimeter: 998.675752833, appTemp: 19.2627703232, barometer: 998.984506851, cloudbase: 1093.61384033, consBatteryVoltage: 0.0, dateTime: 1540854825, dayET: 0.0, dayRain: 0.0, dewpoint: 10.3869357368, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, extraTemp4: 0.0, extraTemp5: 0.0, extraTemp6: 0.0, extraTemp7: 0.0, forecastIcon: 0, forecastRule: 0, heatindex: 19.1111111111, humidex: 20.5701568672, inDewpoint: 9.63329898111, inHumidity: 52.0, insideAlarm: 0, inTemp: 19.7777777778, leafTemp1: 0.0, leafTemp2: 0.0, leafTemp3: 0.0, leafTemp4: 0.0, leafWet1: 0.0, leafWet2: 0.0, leafWet3: 0.0, leafWet4: 0.0, maxSolarRad: 930.93994079, monthET: 0.0, monthRain: 0.0, outHumidity: 57.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 19.1111111111, pressure: 998.288070605, radiation: 0.0, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, stormRain: 0.0, stormStart: 943873200, sunrise: 1540810800, sunset: 1540810800, trendIcon: -1, txBatteryStatus: 1, usUnits: 16, UV: 0.0, windchill: 19.1111111111, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, windSpeed10: 0.0, yearET: 0.0, yearRain: 0.0
(30-10-2018, 00:01)41south Wrote: [ -> ]As an aside I think this problem may also be upsetting the Davis/Vantage data output, I've been trying to get my station going with Weewx but there are some issues with the date being sent with the data. I suspect it's related?? Here is a data capture -- note that the first REC data blocks have a date of 2019-09-11 (And are NZST - should be NZDT), whereas the LOOP packets have the correct date


REC:    2019-09-11 12:05:00 NZST (1568160300) appTemp: 23.7946336801, barometer: 996.241532442, cloudbase: 1192.83426336, consBatteryVoltage: None, dateTime: 1568160300, dewpoint: 13.2578694156, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 22.7777777778, highRadiation: 8.0, highUV: 0.0, humidex: 25.7175378458, inDewpoint: 12.5050008741, inHumidity: 48.0, inTemp: 24.2222222222, interval: 5, leafTemp1: 0.0, 
. . .

Hi 41south,

The date 2019-09-11, based on the timestamp of 1568160300, is 11 September 2019, so NZST would be in force at that time not NZDT.

Gregg
That's true - but it's a rouge date in the data never-the-less Smile
(30-10-2018, 00:01)41south Wrote: [ -> ]As an aside I think this problem may also be upsetting the Davis/Vantage data output, I've been trying to get my station going with Weewx but there are some issues with the date being sent with the data. I suspect it's related??

According to some old posts posts on the forum from an Weewx user, seems that Weewx occasionally also read some values from the Data Logger (all other softwares I know, only do it at start-up, and just if the Use Data Logger option is enabled). So, its possible that there is relation, because if the weather station clock is wrong, the records stored on the hardware Data Logger will have a wrong timestamp.

I hope this issue was definitively fixed on v7.0 b008 (2018-10-30).
I'm testing it during the last 2 hours, forcing NTP updates and RTC syncs at each 10 secs, and even when the NTP update fails (which was causing the issue) the date and time remains correct.
Please give it a try and report back. Thanks.
This was my RTC debug output after the 008 update but date is ok so far

SDK version:2.0.0(5a875ba)
Farylink Technology Co., Ltd. v1.0.0.2
May 11 2017 22:23:58
OK
RTC current date: Jun 00 2018
RTC current time: 16:38:51
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 03:38:52
RTC adjusted to local time: 16:38:52
RTC current date: Jun 00 2018
RTC current time: 16:38:52

Jun 00 2018 seems random
Interesting...

If you wish, try this:

In NET tab, find this:

Code:
//RTC.adjust(DateTime(year(), month(), day(), hour(), minute(), second()));        // Adjust RTC with local time        
RTC.adjust(local);

and replace with this:

Code:
RTC.adjust(DateTime(year(), month(), day(), hour(), minute(), second()));        // Adjust RTC with local time        
//RTC.adjust(local);

Theoretically it should give the same result, but, strangely not always.
I think that looks better ?

AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
Farylink Technology Co., Ltd. v1.0.0.2
May 11 2017 22:23:58
OK
RTC current date: Jun 00 2018
RTC current time: 18:54:41
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 05:54:41
RTC adjusted to local time: 18:54:41
RTC current date: Oct 30 2018
RTC current time: 18:54:41
Hello together,

I'm wondering why 41south has non valid dates reported by the RTC. Since my RTC reports always the correct time at booting up, maybe 41south has two overlayed problems.

At the moment I'm trying to track down where the error occurs in my case.
Code:
AT version:1.2.0.0(Jul  1 2016 20:04:45)
SDK version:1.5.4.1(39cb9a32)
Ai-Thinker Technology Co. Ltd.
Dec  2 2016 14:21:16
OK
RTC current date: Oct 30 2018
RTC current time: 18:19:22
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 17:19:23
RTC adjusted to local time: 18:19:23
RTC current date: Oct 30 2018
RTC current time: 18:19:22


WiFi connection is ON
Timestamp: 1540923639
Timestamp: 1540923699
Timestamp: 1540923759
Timestamp: 1540923819
Timestamp: 1540923879
Timestamp: 1540923939
Timestamp: 1540923999
Timestamp: 1540924059
Timestamp: 1540924119
Timestamp: 1540924179
Timestamp: 1540924239
Timestamp: 1540924299
RTC current date: Oct 30 2018
RTC current time: 18:31:39
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 17:31:39
RTC adjusted to local time: 18:31:39
RTC current date: Oct 30 2018
RTC current time: 18:31:39


Timestamp: 1540924358
Timestamp: 1540924418
Timestamp: 1540924480
Timestamp: 1540924540
Timestamp: 1540924600
Timestamp: 1540924660
Timestamp: 1540924720
Timestamp: 1540924780
Timestamp: 1540924840
Timestamp: 1540924900
Timestamp: 1540924960
Timestamp: 1540925020
Timestamp: 1540925080
Timestamp: 1540925140
Timestamp: 1540925200
Timestamp: 1540925260
Timestamp: 1573930119
Timestamp: 1573930179
Timestamp: 1573930239
Timestamp: 1573930299
Timestamp: 1573930359
Timestamp: 1573930419

Im my case the issue does not occur while getting the time from the NTP server but it happens at epoch time 1540925260 corresponding to Tuesday, 30-Oct-18 18:47:40 UTC.
The first request was at UTC time from NTP server: 17:19:23. So the problem happened about 58 minutes after starting the system.

I'm still in debugging mode and curious what happens after the next NTP sync.

Regards,
engolling

Thanks for the help.
Last night I tried a similar procedure, but forcing the NPT updates (which also set the RTC clock) at each 10 secs, however I couldn't reproduce the problem, however I feel that the problem is there somewhere.

The most strange to me is that the functions to sync of the RTC and system time with NTP are part of the code since long time, and they are working. Something is messing with the RTC, which by turn will incorrectly set the system time, possibly when he syncprovider function runs (this function sync the system time with the RTC time every hour, and exists for the case the weather station doesn't have Internet connection). This is done this way since first software versions, without any problem.
So from where the bug was came? and where is it? Smile

Tonight I will return to the bug hunted.
Pages: 1 2 3 4 5 6 7