Motorola V186 User Manual - Page 146

System Time Control Actions, NTP Clock Synchronization

Page 146 highlights

Clock Functions and Synchronization system table, it also changes the RTU time and date. For more information on the Time & Date database system table, see Appendix C: Database Tables and Data Types in the ACE3600 STS User Guide. The user can update the same Time & Date database system table (HH:MM:SS) using the Application Programmer database monitor function. In this case, synchronization is direct (no time zone aspect.) For information on monitoring a database table, see the Application Programmer chapter of the ACE3600 STS User Guide. System Time Control Actions • GPS Connection - An RTU which is connected to a GPS receiver continuously polls the GPS time and synchronizes itself. Because the clock source is reliable, this RTU can be used to synchronize the rest of the system. See the Global Positioning System (GPS) section below. • NTP Connection - An RTU which is connected to an NTP server continuously polls the NTP server(s). Because the clock source is reliable, this RTU can be used to synchronize the rest of the system. The accuracy of NTP time depends on the link to the NTP server. It can be 1 millisecond in a LAN where the NTP server resides on the same network, and up to 100 milliseconds if using wireless media such as GPRS or TETRA. See the NTP Clock Synchronization section below. If the synchronizing RTU is in a different time zone than the RTU being synchronized, the system will adjust the time accordingly; the receiving RTU will add the time zone of the sender to the global time (GMT) and use this. If only one of the two RTUs involved is configured for time zone support, the synchronization will proceed as if both sites are in the same time zone. Note: A legacy MOSCAD RTUs is treated as an RTU which is not configured for time zone support. Note: In systems with I/O expansion, clock synchronization of the expansion modules is controlled by the main CPU. In addition, a sequencing mechanism ensures that time tags and timer events are sequenced properly in chronological order. NTP Clock Synchronization The Network Time Protocol (NTP) can be used as an external clock source to synchronize the ACE3600 RTU over IP with one or more NTP servers. In the MOSCAD system, the NTP works in client/server mode, in which a client RTU polls another server and gets a reply. The server can be another RTU operating NTP, or a host (PC, Unix, Linux). NTP poll the server RTU every 2 seconds, every 4 seconds, 8 and so on, up to a poll every 17 minutes. NTP provides client accuracies typically within a millisecond on LANs and up to 100 milliseconds on WANs (Internet, GPRS). Any 142

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185

Clock Functions and Synchronization
system table, it also changes the RTU time and date. For more information on the
Time & Date database system table, see Appendix C: Database Tables and Data
Types in the ACE3600 STS User Guide.
The user can update the same Time & Date database system table (HH:MM:SS)
using the Application Programmer database monitor function. In this case,
synchronization is direct (no time zone aspect.) For information on monitoring a
database table, see the Application Programmer chapter of the ACE3600 STS
User Guide.
System Time Control Actions
GPS Connection – An RTU which is connected to a GPS receiver continuously
polls the GPS time and synchronizes itself. Because the clock source is reliable,
this RTU can be used to synchronize the rest of the system. See the Global
Positioning System (GPS) section below.
NTP Connection – An RTU which is connected to an NTP server continuously
polls the NTP server(s). Because the clock source is reliable, this RTU can be
used to synchronize the rest of the system. The accuracy of NTP time depends on
the link to the NTP server. It can be 1 millisecond in a LAN where the NTP server
resides on the same network, and up to 100 milliseconds if using wireless media
such as GPRS or TETRA. See the NTP Clock Synchronization section below.
If the synchronizing RTU is in a different time zone than the RTU being synchronized,
the system will adjust the time accordingly; the receiving RTU will add the time zone of
the sender to the global time (GMT) and use this. If only one of the two RTUs involved is
configured for time zone support, the synchronization will proceed as if both sites are in
the same time zone.
Note: A legacy MOSCAD RTUs is treated as an RTU which is not configured for time
zone support.
Note: In systems with I/O expansion, clock synchronization of the expansion modules is
controlled by the main CPU.
In addition, a sequencing mechanism ensures that time tags
and timer events are sequenced properly in chronological order.
NTP Clock Synchronization
The Network Time Protocol (NTP) can be used as an external clock source to
synchronize the ACE3600 RTU over IP with one or more NTP servers.
In the MOSCAD system, the NTP works in client/server mode, in which a client RTU
polls another server and gets a reply.
The server can be another RTU operating NTP, or a
host (PC, Unix, Linux). NTP poll the server RTU every 2 seconds, every 4 seconds, 8
and so on, up to a poll every 17 minutes. NTP provides client accuracies typically within
a millisecond on LANs and up to 100 milliseconds on WANs (Internet, GPRS). Any
142