Motorola V186 User Manual - Page 150

The M-OPC server uses OPC Data Access DA V2.05. The server enables the clients

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

SCADA System Components All the M-OPC components run on a standard PC hardware platform that supports both MS Windows 2000 Pro and MS Windows XP Pro. The M-OPC solution uses a standard client/server architecture. The Control center components include Client(s) (SCADA software or other applications), M OPC server, MDLC driver and Field Interface Unit -FIU (ACE3600, MOSCAD or MOSCAD-L CPU). The FIU provides MDLC networking and various media connectivity to the RTUs. The M-OPC offers the following functionality: • Standard interface between ACE3600 and MOSCAD family RTUs and many control center SCADA managers. • Support of special features unique to Motorola RTUs. • Support of the MDLC protocol and all Motorola RTU types, i.e., ACE3600, MOSCAD, MOSCAD-L and MOSCAD-M. The M-OPC server uses OPC Data Access (DA) V2.05. The server enables the clients to organize the field data according to the OPC logical object model and read/write data either synchronously or asynchronously. It automatically updates clients when new groups are created and also enables SCADA clients to retrieve new groups without having to restart the server. The server uses the MDLC driver to: • Poll the RTU databases • Send commands to the RTUs • Receive data bursts from the RTUs The server scheduler is responsible for scheduling the polling of RTU data. Data polling can be performed in periodic intervals or upon specific requests from clients. Schedules are set using the M-OPC Monitoring and Setup Tool. The scheduler optimizes the communications with the RTUs to minimize the MDLC network communication load. This feature is extremely important in radio networks. The server holds the information received from the RTUs in a cache database. The cache reflects the latest value of the data as well as its quality and the server time-stamp. 146

  • 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
All the M-OPC components run on a standard PC hardware platform that supports both
MS Windows 2000 Pro and MS Windows XP Pro.
The M-OPC solution uses a standard client/server architecture. The Control center
components include Client(s) (SCADA software or other applications), M OPC server,
MDLC driver and Field Interface Unit –FIU (ACE3600, MOSCAD or MOSCAD-L
CPU). The FIU provides MDLC networking and various media connectivity to the RTUs.
The M-OPC offers the following functionality:
•
Standard interface between ACE3600 and MOSCAD family RTUs and many
control center SCADA managers.
•
Support of special features unique to Motorola RTUs.
•
Support of the MDLC protocol and all Motorola RTU types, i.e., ACE3600,
MOSCAD, MOSCAD-L and MOSCAD-M.
The M-OPC server uses OPC Data Access (DA) V2.05. The server enables the clients to
organize the field data according to the OPC logical object model and read/write data
either synchronously or asynchronously.
It automatically updates clients when new
groups are created and also enables
SCADA clients to retrieve new groups
without having to restart the server.
The server uses the MDLC driver to:
•
Poll the RTU databases
•
Send commands to the RTUs
•
Receive data bursts from the
RTUs
The server scheduler is responsible for
scheduling the polling of RTU data.
Data polling can be performed in
periodic intervals or upon specific
requests from clients. Schedules are
set using the M-OPC Monitoring and
Setup Tool. The scheduler optimizes
the communications with the RTUs to
minimize the MDLC network
communication load. This feature is
extremely important in radio
networks.
The server holds the information
received from the RTUs in a cache database. The cache reflects the latest value of the
data as well as its quality and the server time-stamp.
146