ezTime — pronounced "Easy Time" — is a very easy to use Arduino time and date library that provides NTP network time lookups, extensive timezone support, formatted time and date strings, user events, millisecond precision and more.
MIT License
327
stars
92
forks
source link
Can not get network connection for NTP to work, not on WiFi #54
2:05:06.350 -> 192.168.0.99
12:05:06.385 -> Working ...
12:05:17.380 -> Working 2 ...
12:05:17.380 ->
12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.574 UTC
12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.577 UTC
12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.580 UTC
12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.583 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.586 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.589 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.592 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.596 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.599 UTC
12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.602 UTC
12:05:17.415 ->
12:05:17.415 -> Those milliseconds between the first and the last line ...
12:05:17.415 ->
12:05:17.415 -> ... most of that is spent sending to the serial port.
12:05:17.415 ->
12:05:17.415 ->
12:05:17.415 ->
12:05:17.415 -> And ezTime is not making those milliseconds up either.
12:05:17.415 ->
12:05:17.415 -> ... Stick around as we do an NTP request every minute.
12:05:17.449 ->
12:05:17.449 -> ezTime debug level set to INFO
12:05:20.804 -> Querying pool.ntp.org ... ERROR: No network
12:05:25.808 -> Querying pool.ntp.org ... ERROR: No network
I have an NTP server at 192.168.0.5, and my IP is 192.168.0.99. Tried the pool.ntp.org site and still no joy.
2:05:06.350 -> 192.168.0.99 12:05:06.385 -> Working ... 12:05:17.380 -> Working 2 ... 12:05:17.380 -> 12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.574 UTC 12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.577 UTC 12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.580 UTC 12:05:17.380 -> Thursday, 01-Jan-70 00:00:11.583 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.586 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.589 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.592 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.596 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.599 UTC 12:05:17.415 -> Thursday, 01-Jan-70 00:00:11.602 UTC 12:05:17.415 -> 12:05:17.415 -> Those milliseconds between the first and the last line ... 12:05:17.415 -> 12:05:17.415 -> ... most of that is spent sending to the serial port. 12:05:17.415 -> 12:05:17.415 -> 12:05:17.415 -> 12:05:17.415 -> And ezTime is not making those milliseconds up either. 12:05:17.415 -> 12:05:17.415 -> ... Stick around as we do an NTP request every minute. 12:05:17.449 -> 12:05:17.449 -> ezTime debug level set to INFO 12:05:20.804 -> Querying pool.ntp.org ... ERROR: No network 12:05:25.808 -> Querying pool.ntp.org ... ERROR: No network
I have an NTP server at 192.168.0.5, and my IP is 192.168.0.99. Tried the pool.ntp.org site and still no joy.
UNO/Ethernet card. Suggestions? Thx,P