EasyManua.ls Logo

LEM DCBM 400 Series - 7.8. Time Management; 7.8.1. Time Synchronization; 7.8.1.1. Overview; 7.8.1.2. General Constraints

LEM DCBM 400 Series
95 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Page 86/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com


 
• Proper synchronization is required for any new transaction
• Synchronization expires after 48 hours
• It cannot be achieved during transactions
 
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      (< 24 hours period),
considering 48 hours expiration.
The time management is “Info time”. The DCBM does not support “System time” in this version.
 
Two time synchronization modes are available:
• Synchronization by NTP
• Synchronization by a command sent to the DCBM
/settings API o󰀨ers a setting to switch from one mode to another: /ntp/activated in /
settings API. Switching mode has no e󰀨ect 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
!

Table of Contents