Motorola V186 User Manual - Page 108

Configuring NTP Servers, User Protocol over IP, Dynamic IP Address, MDLC over IP Port Routing

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 108 highlights

Communications Configuring NTP Servers An Ethernet or RS232 PPP port can be configured for NTP protocol (NTP is UDP port number 123.) In this case, the RTU will retrieve its time from a set of NTP servers specified by the user. The clock offset between the RTU and these servers depends on network delays, and may be up to 100 milliseconds in some wireless media. The clock offset on LAN in the same Ethernet network is approximately 1 millisecond. Note: It is possible to define an NTP server with a full host name (e.g. www.mysite.com). To do so, the user must set DNS servers for this port, either statically, or from a DHCP server or PPP modem. User Protocol over IP Both Ethernet and PPP ports provide an interface for a user application written in the 'C' Toolkit using MOSCAD_socket() functions, also known as "User protocol over IP". An MDLC over IP port can serve a user application at the same time as it serves MDLC which is built in the socket API. MDLC takes one logical UDP port number (2002 by default); other applications can use other TCP or UDP port numbers. For more information on the 'C' Toolkit socket functions, see the ACE3600 RTU 'C' Toolkit User Guide. Dynamic IP Address Many wireless networks do not allocate a fixed IP address to a PPP modem (such as the GPRS network). For the FEP to communicate with the RTU it must know its address or host name. Since these networks do not provide a name for each modem, there is no option of setting them in the FEP beforehand. In this case, the FEP should not be assigned an IP conversion table with that link ID (port). The RTUs should be associated with a table which has the FEP's IP address. If the network operator assigns a host name to the FEP instead of a numeric address, this can be set in the IP conversion table. When the RTU detects that its modem is connected, it will notify this address, the FEP, of its new IP address, thus updating its table in runtime. Since this process does not guarantee that the FEP will be updated, it is highly recommended that user application periodically send a message to the FEP. For example, if the user application expects an interrogation every two minutes from the FEP, and it has not received that, it will send a message to the FEP. This will update the RTU address in the FEP. MDLC over IP Port Routing In the example mentioned in Dynamic IP Address above, for RTU-to-RTU (modem to modem) communication, set 'Enable routing of MDLC over IP port' parameter in the FEP. Then assign to the RTUs an IP conversion table which list the RTUs' site IDs as having the FEP IP address. 104

  • 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
Communications
Configuring NTP Servers
An Ethernet or RS232 PPP port can be configured for NTP protocol (NTP is UDP port
number 123.) In this case, the RTU will retrieve its time from a set of NTP servers
specified by the user. The clock offset between the RTU and these servers depends on
network delays, and may be up to 100 milliseconds in some wireless media. The clock
offset on LAN in the same Ethernet network is approximately 1 millisecond.
Note: It is possible to define an NTP server with a full host name (e.g. www.mysite.com).
To do so, the user must set DNS servers for this port, either statically, or from a DHCP
server or PPP modem.
User Protocol over IP
Both Ethernet and PPP ports provide an interface for a user application written in the ‘C’
Toolkit using MOSCAD_socket() functions, also known as “User protocol over IP”. An
MDLC over IP port can serve a user application at the same time as it serves MDLC
which is built in the socket API. MDLC takes one logical UDP port number (2002 by
default); other applications can use other TCP or UDP port numbers. For more
information on the ‘C’ Toolkit socket functions, see the ACE3600 RTU ‘C’ Toolkit User
Guide.
Dynamic IP Address
Many wireless networks do not allocate a fixed IP address to a PPP modem (such as the
GPRS network). For the FEP to communicate with the RTU it must know its address or
host name. Since these networks do not provide a name for each modem, there is no
option of setting them in the FEP beforehand. In this case, the FEP should not be
assigned an IP conversion table with that link ID (port). The RTUs should be associated
with a table which has the FEP’s IP address. If the network operator assigns a host name
to the FEP instead of a numeric address, this can be set in the IP conversion table. When
the RTU detects that its modem is connected, it will notify this address, the FEP, of its
new IP address, thus updating its table in runtime.
Since this process does not guarantee that the FEP will be updated, it is highly
recommended that user application periodically send a message to the FEP. For example,
if the user application expects an interrogation every two minutes from the FEP, and it
has not received that, it will send a message to the FEP. This will update the RTU address
in the FEP.
MDLC over IP Port Routing
In the example mentioned in Dynamic IP Address above, for RTU-to-RTU (modem to
modem) communication, set ‘Enable routing of MDLC over IP port’ parameter in the
FEP. Then assign to the RTUs an IP conversion table which list the RTUs’ site IDs as
having the FEP IP address.
104