Motorola V186 User Manual - Page 111

MDLC over LAN/Ethernet

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

Communications MDLC over LAN/Ethernet The ACE3600 RTU can communicate over Ethernet media, via the onboard Ethernet port or 10/100BT plug-in ports. The figure below illustrates an example of a SCADA system with IP Gateway and ACE3600 RTUs connected to Ethernet LAN: SCADA Central STS LINE 1 RS-232 IP Gateway STS Ethernet 1 IP Network Ethernet 2 STS 10BaseT RTU-IP1 RS-232 10BaseT RTU-IP2 on Ethernet on-board Port Ethernet 3 10BaseT RTU-IP3 on Ethernet Plug-in Port With SCADA systems the ACE3600 RTU can be connected to Ethernet/LAN as an FEP (FIU) for a SCADA, and an RTU. It communicates with MDLC over IP between FEP/IP Gateway and RTU. The IP Gateway unique functionality provides an API over TCP/IP API, for the SCADA PC. It provides the SCADA with the current values of the RTU tables and with the events (Bursts) that are associated with each entity. The ACE3600 does not have that functionality built-in and requires an IP Gateway. Unlike IP Gateway, ACE3600 can be connected to several Ethernet connections. They can reside on the same or on different network subnet masks, and are distinguished from one another by a link name. 107

  • 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
MDLC over LAN/Ethernet
The ACE3600 RTU can communicate over Ethernet media, via the onboard Ethernet port
or 10/100BT plug-in ports.
The figure below illustrates an example of a SCADA system with IP Gateway and
ACE3600 RTUs connected to Ethernet LAN:
10BaseT
RS-232
LINE 1
RS-232
SCADA
Central
STS
Ethernet 1
IP
Network
Ethernet 3
RTU-IP2
RTU-IP3
IP
Gateway
STS
Ethernet 2
RTU-IP1
10BaseT
10BaseT
STS
on Ethernet
on-board
Port
on Ethernet
Plug-in Port
With SCADA systems the ACE3600 RTU can be connected to Ethernet/LAN as an FEP
(FIU) for a SCADA, and an RTU. It communicates with MDLC over IP between FEP/IP
Gateway and RTU. The IP Gateway unique functionality provides an API over TCP/IP
API, for the SCADA PC. It provides the SCADA with the current values of the RTU
tables and with the events (Bursts) that are associated with each entity. The ACE3600
does not have that functionality built-in and requires an IP Gateway.
Unlike IP Gateway, ACE3600 can be connected to several Ethernet connections. They
can reside on the same or on different network subnet masks, and are distinguished from
one another by a link name.
107