Motorola V186 User Manual - Page 151

IP Gateway, Legacy ModBus FEP

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

SCADA System Components During the M-OPC Server operation, various operational data are collected and logged for user diagnostics purposes. IP Gateway TCP/IP is a protocol in common use on Ethernet data highways such as the World Wide Web and others. The MOSCAD IP Gateway (was MCP-T) supports this connectivity. The MOSCAD IP Gateway is packaged in the small NEMA 4 enclosure, contains an 8Amp power supply/charger, battery, and communication device (radio or wireline modem) according to the needs of the system. The IP Gateway module has communication ports but it does not support any I/O modules. Both 10BaseT and AIX connectors are available to connect the IP Gateway to the 10 Mbps Ethernet LAN. The IP Gateway is a gateway-a real-time protocol converter-that connects MDLC on its communication medium to TCP/IP. It does not contain a database. It is configured by simply assigning an MDLC and an IP address for their respective systems' use; a configuration software program is provided with the IP Gateway to ease this task. An API is also provided which the system engineer must use to develop a driver between the programs in the server that require data from the IP Gateway and the IP Gateway itself. Contact your Motorola Data Specialists to determine if a driver is already available for the host hardware/software being used. Legacy ModBus FEP ModBus is a wireline protocol in common use in SCADA markets (now also available on TCP/IP networks). It is supported by many SCADA Manager vendors and it is traditionally used in MOSCAD systems at the central. ModBus drivers typically expect prompt communications between the computer and the field units; they do not tolerate well the random delays encountered when a shared communication medium is used. The legacy MOSCAD Communications Processor for ModBus (MCP-M) was designed to interface ModBus to both MDLC and the shared media. MCP-M exists in many existing MOSCAD system where additional ACE3600 RTUs can be installed. The MCP-M contains a Series 400 CPU module with a RAM expansion board and a special FEP program. The MCP-M is packaged in the small NEMA 4 enclosure, contains the 8Amp power supply/charger, battery, and communications device (radio or wireline modem) according to the needs of the system. The FEP program retains the communication ports but does not support any I/O modules. A serial data cable connects between either Port 1B or Port 2 (or both-the MCP-M supports two simultaneous ModBus sessions) on the CPU module and the appropriate COM port on the PC computer; ModBus data typically at 19.2 kbps exists on this connection. The MCP-M maintains an internal database of all the reportable data from all of the MOSCAD RTUs in the system. A System Builder software program is provided with the MCP-M to ease this task: it reads the export file created by the MOSCAD Programming ToolBox for each of the many RTUs' applications and prompts the system engineer to identify which data items are to be collected and which are not. Each identified data item 147

  • 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
SCADA System Components
During the M-OPC Server operation, various operational data are collected and logged
for user diagnostics purposes.
IP Gateway
TCP/IP is a protocol in common use on Ethernet data highways such as the World Wide
Web and others. The MOSCAD IP Gateway (was MCP-T) supports this connectivity.
The MOSCAD IP Gateway is packaged in the small NEMA 4 enclosure, contains an
8Amp power supply/charger, battery, and communication device (radio or wireline
modem) according to the needs of the system. The IP Gateway module has
communication ports but it does not support any I/O modules. Both 10BaseT and AIX
connectors are available to connect the IP Gateway to the 10 Mbps Ethernet LAN.
The IP Gateway is a gateway—a real-time protocol converter—that connects MDLC on
its communication medium to TCP/IP. It does not contain a database. It is configured by
simply assigning an MDLC and an IP address for their respective systems’ use; a
configuration software program is provided with the IP Gateway to ease this task. An
API is also provided which the system engineer must use to develop a driver between the
programs in the server that require data from the IP Gateway and the IP Gateway itself.
Contact your Motorola Data Specialists to determine if a driver is already available for
the host hardware/software being used.
Legacy ModBus FEP
ModBus is a wireline protocol in common use in SCADA markets (now also available on
TCP/IP networks). It is supported by many SCADA Manager vendors and it is
traditionally used in MOSCAD systems at the central. ModBus drivers typically expect
prompt communications between the computer and the field units; they do not tolerate
well the random delays encountered when a shared communication medium is used. The
legacy MOSCAD Communications Processor for ModBus (MCP-M) was designed to
interface ModBus to both MDLC and the shared media. MCP-M exists in many existing
MOSCAD system where additional ACE3600 RTUs can be installed.
The MCP-M contains a Series 400 CPU module with a RAM expansion board and a
special FEP program. The MCP-M is packaged in the small NEMA 4 enclosure, contains
the 8Amp power supply/charger, battery, and communications device (radio or wireline
modem) according to the needs of the system. The FEP program retains the
communication ports but does not support any I/O modules. A serial data cable connects
between either Port 1B or Port 2 (or both—the MCP-M supports two simultaneous
ModBus sessions) on the CPU module and the appropriate COM port on the PC
computer; ModBus data typically at 19.2 kbps exists on this connection.
The MCP-M maintains an internal database of all the reportable data from all of the
MOSCAD RTUs in the system. A System Builder software program is provided with the
MCP-M to ease this task: it reads the export file created by the MOSCAD Programming
ToolBox for each of the many RTUs’ applications and prompts the system engineer to
identify which data items are to be collected and which are not. Each identified data item
147