WeatherDuino Forum

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

(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

(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:


and replace with this:


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.

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?

Tonight I will return to the bug hunted.