Page 87/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com
7.8.1.4. Command time synchronization
Command time synchronization requires nothing more than a HTTP request, consisting in writing
a timestamp on field
/time/utc
in
/settings
API.
Timestamp shall be UTC time, and compliant with ISO-8601 format.
Here is an example of writable timestamp: “
2020-01-01T14:00:00Z
”
It is not necessary to specifically switch off NTP if used before triggering Command time
synchronization request, as it is done automatically.
7.8.1.5. NTP synchronization
Network Time Synchronization allows reliable and automatic synchronization. NTP allows using a
large amount of public and precise time references.
Use of NTP requires the following actions in
/settings
API:
•
Configure at least one server, by entering an IP or URL in field
ntp/servers/ipAddress
, and the
required port in field
ntp/servers/port
• Switch
ntp/activated
to “true”
123 is the default IANA port for NTP.
No synchronization is allowed during a transaction
An attempt of NTP synchronization is achieved:
•
As configured in field
ntp/syncPeriod
in
/settings
API
• On expiration of the synchronization
•
Or at the end of the transaction, if synchronization expired during it
• On startup of the DCBM
• When switching to NTP mode
An attempt of NTP synchronization can end with the following outcomes:
•
The synchronization succeeded. Time of valid synchronization is saved, and synchronization becomes
valid for the next 48 hours.
• The synchronization failed. Synchronization status is not discarded; it stays valid until expiration (48
hours after the last valid synchronization).
i
!
Summary of Contents for DCBM 400 Series
Page 95: ......
