TABLE OF CONTENTS

Restart your Device after reconnecting it:
Testing NTP:
Frequently Asked Questions:
- Why is my clock stopped on my display?
- What do I do if the Date is off by months?
Helpful Articles:

When a Wall Display/CPU/DAKboard OS device has been powered off or disconnected from the internet for a length of time, the internal clock may gain or lose time. When reconnected to the internet, the DAKboard device will automatically update the time. However, sometimes this update process is delayed, and an "incorrect date/time" or "Your clock is behind" message will appear. Try the step below to resolve the issue or determine the cause of the failure.

Restart your Device after reconnecting it:

If your device is connected to the internet, leave it powered on for about 5-10 minutes to give it enough time to sync, then restart it by unplugging the power and plugging it back in.

If the time still does not update, you may be unable to access the time servers from your location due to a networking issue. If you are comfortable with accessing the command-line interface for the device and troubleshooting the network issue, see our article DAKboard OS SSL/SSH Configuration and Use to learn how to access the command line:

Testing NTP:

Identify the status of the service, and note the 'System clock synchronized' and the 'NTP Service' sections for feedback:

timedatectl status

Local time: Wed 2025-07-16 10:23:29 EDT
Universal time: Wed 2025-07-16 14:23:29 UTC
RTC time: Wed 2025-07-16 14:23:29
Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

If the NTP service shows off, try to restart the service or the device. Restarts of the service are performed by running the following:

sudo timedatectl restart

NTP will have several fallback servers, which are all located in the following configuration file and are used for obtaining time sync data. You can find them by following the example below; most systems will be

0.debian.pool.ntp.org
1.debian.pool.ntp.org
2.debian.pool.ntp.org
3.debian.pool.ntp.org

Advanced: NTP servers may be manually changed by uncommenting the 'FallbackNTP' line by using an editor like Nano and making changes to the domains listed:

sudo nano /etc/systemd/timesyncd.conf

#  This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the timesyncd.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# See timesyncd.conf(5) for details.

[Time]
#NTP=
#FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048
#ConnectionRetrySec=30
#SaveIntervalSec=60

Pull any number of the servers and perform an IP from ping to find the IP as shown. This will tell you if you can reach the NTP server with a ping, and the IP for additional testing in the next step:

ping debian.pool.ntp.org

PING debian.pool.ntp.org (74.208.79.7) 56(84) bytes of data.

Perform a UDP Netcat to check the UDP 23 port, which is used for the NTP of the IP you gained from the ping in the previous step. Below is a successful response example for IP 38.229.53.9:

nc -z -v -u 74.208.79.7 23

Connection to 74.208.79.7 23 port [udp/*] succeeded!

More advanced details on the timedatectl service are available to be reviewed at the following:

https://wiki.archlinux.org/title/systemd-timesyncd

Frequently Asked Questions:

Below are the most Frequently Asked Questions about the <Block Name Here> block:

Why is my clock stopped on my display?

A DAKOS device should never have its clock stop. The clock is managed by the internal clock of the CPU. If it remains frozen, this could indicate that the CPU is offline and can no longer reach the NTP server. Try rebooting the CPU by unplugging it and plugging it back in. If you get the No Internet message, you could be offline. Use our article Trouble Connecting To A WiFi Network to determine the cause. If the display comes back up but the clock is still frozen, use the steps above to check and see if you can access the NTP servers.

What do I do if the Date is off by months?

This could also indicate that the CPU cannot reach the NTP servers. If you are connected to the internet, allow the display to stay connected for 5 minutes. If the Date does not update by that time, try unplugging the CPU and plugging it back in to allow the NTP server to update. If it still fails, use the steps above to check and see if you can access the NTP servers.