Instructions

UM-0085-B09 DT80 Range User Manual Page 272
RG
Manually Triggered NTP Requests
When background NTP requests are enabled in the profile, a request will be performed:
• at the configured time intervals
• following hard reset
• following wake from sleep
• following any change to any of the NTP profile settings
An NTP request can also be triggered manually, regardless of whether or not background NTP updates are enabled.
This is done using the NTP command. This command may then be included in a schedule, inside an ALARM or DO
statement, which allows more control over the timing of NTP requests.
The NTP command will perform an immediate NTP request, using the settings defined in the profile (the
BACKGROUND_ENABLE, BACKGROUND_PERIOD and BACKGROUND_WAKEUP_DELAY settings will be ignored) .
For example:
NTP
NTP: Adjusting time (-254 ms)
NTP
NTP: No time change required
Checking NTP Status
System variable 26SV reports the status of the last NTP request, as follows
26SV
Meaning
0
No NTP requests have been performed
1
Gradual time adjustment in progress
2
Time adjustment completed successfully
-1
Could not resolve NTP server name
-2
NTP request failed: could not connect to server, or no response within timeout time
-3
Required time adjustment was not performed because it exceeded the
MAX_SLEW_CORRECTION
and
MAX_JUMP_CORRECTION
settings.
-4
NTP request failed due to an internal DT80 error
-5
Daily limit of 50 requests to 0.datataker.pool.ntp.org was exceeded
System variable 27SV returns the discrepancy between the DT80's time and the NTP server, as at the last successful
NTP request. If the NTP request resulted in the DT80 clock being adjusted, 27SV holds the discrepancy before
the
correction was applied. For example, a value of -150 indicates that the logger time was 150ms ahead of the NTP server
time. 27SV=0 if no NTP requests have been made. Any request that results in a "time jump" adjustment will also be
logged to the event log.