Page 86/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com
7.8. Time management
7.8.1. Time synchronization
7.8.1.1. Overview
• Proper synchronization is required for any new transaction
• Synchronization expires after 48 hours
• It cannot be achieved during transactions
7.8.1.2. General constraints
Time synchronization is a prerequisite to new transactions. At a given time, synchronization is
either valid or outdated.
A time synchronization remains valid for 48 hours. Any successful synchronization restarts the
timer for a new 48 hours span. No event can shorten or extend this duration, including power
down.
No time synchronization can be achieved during transactions. This 48 hours expiration can happen
in any state of the DCBM, including during transactions and power down.
It is recommended to achieve time synchronization
at least once a day
(< 24 hours period),
considering 48 hours expiration.
The time management is “Info time”. The DCBM does not support “System time” in this version.
7.8.1.3. Synchronization solutions
Two time synchronization modes are available:
• Synchronization by NTP
• Synchronization by a command sent to the DCBM
/settings
API offers a setting to switch from one mode to another:
/ntp/activated
in
/
settings
API. Switching mode has no effect on status of synchronization or on the 48 hours
timeout.
In case NTP is used (
ntpEnabled
= true), achieving a time synchronization by command
automatically disables
/ntp/activated
boolean (i.e. sets
ntpEnabled
= false)
!
i
!
Summary of Contents for DCBM 400 Series
Page 95: ......
