Motorola V186 User Manual - Page 145

User Time Control Actions, For information on the Sync function, see Appendix B: Ladder Diagram

Get Motorola V186 - Cell Phone - GSM PDF manuals and user guides View all Motorola V186 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 145 highlights

Clock Functions and Synchronization In ACE3600 RTUs, a new MLDC extended time synchronization can be enabled which includes the synchronizing RTU's password. In this case, all RTUs in the system must use the same password. This extended time synchronization also enables synchronizing two RTUs in different time zones, and better accuracy than the MOSCAD MDLC legacy synchronization. Note that by default, the ACE3600 uses MOSCAD MDLC legacy synchronization (to support IP Gateway and MOSCAD RTUs) which does not include the time zone and password features. Note: An extended time synchronization of two RTUs, where only one is configured for time zone, will proceed as if both RTUs are in the same time zone. The RTU clock can be synchronized during runtime using a number of methods. Before synchronizing the clock, make sure that the appropriate parameters have been configured properly. (See Time Parameter Configuration below.) User Time Control Actions • STS Date & Time utility - From the STS, the user sets the RTU date/time to the PC's date/time (which is limited to second accuracy.) For information on using the Date & Time utility, see the Operation chapter of the ACE3600 STS User Guide. • STS Sync utility - From the STS, the user instructs the local RTU to synchronize (in milliseconds accuracy) the date/time of other RTUs attached to one or all links. It is recommended to synchronize all links, so that the entire system has the same date/time. For information on using the Sync utility, see the Operation chapter of the ACE3600 STS User Guide. Note that MDLC dialup links do not support synchronization. • User Application - The user application (ladder or 'C') can synchronize RTUs on one or all links using the Sync function. It is recommended that an RTU with a reliable clock source synchronize all RTUs in the system once per day to correct clock drift. The requirement for legacy MOSCAD RTUs to synchronize RTUs at least once every 48 days is not relevant to ACE3600 RTUs. However, ACE3600 has a drift of 30 ppm which is 2.6 seconds per day if not connected to an NTP server and/or GPS receiver. The worst case is a drift of 1.8 milliseconds per minute, or 18 milliseconds per 10 minutes. Typical tests shows better results at 1 millisecond per 2 minutes, or 5 millisecond per 10 minutes. The interval of sending a time sync, is proportional to that clock offset/accuracy - sending a sync every 2 minutes assures a 1 millisecond offset typically.) For information on the Sync function, see Appendix B: Ladder Diagram Language in the ACE3600 STS User Guide and 'C' Toolkit for ACE3600 RTUs User Guide. When the user application (ladder or 'C') updates the Time & Date database 141

  • 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
In ACE3600 RTUs, a new MLDC extended time synchronization can be enabled which
includes the synchronizing RTU’s password. In this case, all RTUs in the system must
use the same password. This extended time synchronization also enables synchronizing
two RTUs in different time zones, and better accuracy than the MOSCAD MDLC legacy
synchronization. Note that by default, the ACE3600 uses MOSCAD MDLC legacy
synchronization (to support IP Gateway and MOSCAD RTUs) which does not include
the time zone and password features.
Note: An extended time synchronization of two RTUs, where only one is configured for
time zone, will proceed as if both RTUs are in the same time zone.
The RTU clock can be synchronized during runtime using a number of methods. Before
synchronizing the clock, make sure that the appropriate parameters have been configured
properly. (See Time Parameter Configuration below.)
User Time Control Actions
•
STS Date & Time utility – From the STS, the user sets the RTU date/time to the
PC’s date/time (which is limited to second accuracy.) For information on using
the Date & Time utility, see the Operation chapter of the ACE3600 STS User
Guide.
•
STS Sync utility – From the STS, the user instructs the local RTU to synchronize
(in milliseconds accuracy) the date/time of other RTUs attached to one or all
links. It is recommended to synchronize all links, so that the entire system has the
same date/time. For information on using the Sync utility, see the Operation
chapter of the ACE3600 STS User Guide. Note that MDLC dialup links do not
support synchronization.
•
User Application – The user application (ladder or ‘C’) can synchronize RTUs on
one or all links using the Sync function. It is recommended that an RTU with a
reliable clock source synchronize all RTUs in the system once per day to correct
clock drift.
The requirement for legacy MOSCAD RTUs to synchronize RTUs at least once
every 48 days is not relevant to ACE3600 RTUs. However, ACE3600 has a drift
of 30 ppm which is 2.6 seconds per day if not connected to an NTP server and/or
GPS receiver. The worst case is a drift of 1.8 milliseconds per minute, or 18
milliseconds per 10 minutes. Typical tests shows better results at 1 millisecond
per 2 minutes, or 5 millisecond per 10 minutes. The interval of sending a time
sync, is proportional to that clock offset/accuracy – sending a sync every 2
minutes assures a 1 millisecond offset typically.)
For information on the Sync function, see Appendix B: Ladder Diagram
Language in the ACE3600 STS User Guide and
‘C’ Toolkit for ACE3600 RTUs
User Guide.
When the user application (ladder or ‘C’) updates the Time & Date database
141