30-10-2018, 19:09
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
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: 1573930419Im 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