Home » Motorola Manuals » Mobile Phones » Motorola V186 » Manual Viewer

Motorola V186 User Manual - Page 112

MDLC over ASTRO IV&D

Add to My Manuals
Save this manual to your list of manuals

Page 112 highlights

Communications A number of connection methods are available when configuring an Ethernet-based RTU: 1. Static IP address - The user sets the IP address within the configuration of the device in the STS. To use this method, follow the instructions for configuring an RTU in the Operation chapter in the ACE3600 STS User Guide. All DHCP parameters will remain at default values. 2. DHCP-supplied reserved IP address - For every ACE3600 RTU, an IP address will be reserved within the DHCP server. The link between the RTU and the reservation will be based on unique ID. In the DHCP Server, set the unique ID. The default unique is the MAC address. In the DHCP server, define a reservation for a specific RTU based on its MAC address. 3. DHCP-supplied dynamic IP address - A dynamic IP address is distributed from the DHCP server to the ACE3600 RTUs. The IP address of each ACE device is unpredictable. In this case you will need a DNS server that will resolve the link between the IP address and the RTU. You will have to supply a name for each RTU. This name will be updated within the DNS server along with IP address of the RTU. Within IP conversion table of ACE3600 RTU you will use this DNS name instead of IP address. In order to comply with IP networks standards, all configuration methods described in this chapter are based on standard procedures used in IP networks. MDLC over ASTRO IV&D With SCADA systems, ACE3600 RTUs can be connected to an ASTRO IV&D radio. The ASTRO infrastructure (R6.4 or higher) and radio must support integrated voice and data (named IV&D). This is relevant to Motorola subscriber data radios such as the XTL5000 mobile and XTS2500 portable. The connection to ASTRO IV&D can be made via LAN or via radio. The LAN is called a CEN (Customer Enterprise Network). An IP Gateway or RTU with an Ethernet port can be connected to the CEN. On the other end, an RTU can be connected to an ASTRO IV&D radio via an RS232 data cable. Note that a specific codeplug which supports the data option must be used when programming them. In the figure below, the SCADA central and IP Gateway are connected via LAN to a Customer Enterprise Network (CEN). The CEN is connected via a border router gateway to the ASTRO IV&D infrastructure. An RTU, running MDLC over IP protocol over PPP, is connected via XTL5000 radio using an RS232 data cable. A unique IP address is assigned by the GPRS Gateway Support Node (GGSN) to each RTU according to its radio individual unit ID (UID), such that when a frame is transmitted from the CEN to that IP address, the Packet Data Router (PDR) and Radio Network Gateway (RNG) transmit it to the appropriate radio. 108

Section	Page
Table of Contents	3
ACE3600 System Overview	5
ACE3600 RTU Construction	7
Power Supply Modules	10
12V Backup Battery	11
CPU Modules	12
I/O Modules	14
Digital Input Modules	17
Digital Output Relay Modules	26
Analog Input Modules	35
Analog Output Modules	43
Digital Output and Digital Input FET Modules	49
Mixed I/O Modules	56
Mixed Analog Modules	58
I/O Expansion	60
Expansion Power Supply Module	64
Expansion Module	65
Module Firmware and Operation Modes	66
Expansion Module Power-up and Restart	68
Expansion Module during Run-Time	68
Expansion LAN Switch	69
RTU I/O Expansion - Power Considerations	71
Ordering Information	74
ACE3600 RTU Ordering Flow:	74
List of ACE3600 Models	84
List of ACE3600 Options	86
Mixed Input/Output Modules	87
Mixed Analog Modules	87
I/O Module Cables	88
General Ordering Requirements	89
ACE3600 Installation Guidelines	90
Dimensions	90
Frame Dimensions:	90
Metal Chassis Dimensions:	90
Housing Dimensions:	90
GENERAL SAFETY INFORMATION:	91
Mounting the ACE3600 Frame on a Wall	92
Wall Mount Installation	92
Installing the ACE3600 in a 19\	94
Housing Installation	95
Communications	97
MDLC Protocol	98
MDLC Data Transfer Methods	101
Communication Links	102
RS232 Ports	102
RS485 Ports	103
IP Ports (MDLC over IP)	105
Broadcast and Setcalls	106
New Features for MDLC over IP in ACE3600	106
Multiple IP Ports	106
IP Conversion Table Enhancements	107
Using Host Names	107
Configuring NTP Servers	108
User Protocol over IP	108
Dynamic IP Address	108
MDLC over IP Port Routing	108
MDLC over IP PPP Connections	109
MDLC over IP/LAN Connections	109
MDLC over IP Site Paging	110
MDLC over LAN/Ethernet	111
MDLC over ASTRO IV&D	112
MDLC over iDEN	114
MDLC over Tetra	115
MDLC over IP - Standard Modem	117
MDLC over Null Modem	117
MDLC over GPRS Network	118
IP Conversion Tables	120
Firewall	122
Radio Communications	124
Radio FCC information	125
Conventional and Analog Trunked Radio Modulation Types	126
PL & DPL	126
FCC Reframing (USA only)	127
VHF Splinter Channels (USA only)	127
Analog Trunked Radio Systems	129
Digital Trunked Radio Systems	130
Conventional Radio Interoperability	130
Introduction	130
Channel Monitor Resolution Parameter (MDLC Slot Time)	130
First Warm-up Delay Parameter	130
F1-F2 Repeater Considerations	131
Parameter Setting for Motorola Conventional Radios in MOSCAD / ACE3600 Systems	131
Setting the Parameters in the MOSCAD/MOSCAD-L ToolBox	132
Setting the Parameters in the ACE3600 STS	132
Communication Network	133
Communication Types	134
Network Configurations	135
Simple System	135
Two-Link and Multiple Link Systems	135
Two-Zone System	136
Multiple Zone System	137
MDLC Encryption	139
Overview	139
Encryption Keys	141
Encryption in the STS/ToolBox MDLC Driver	142
Security Administration Tool	143
MDLC Encryption Implementation Considerations	143
Clock Functions and Synchronization	144
RTU Clock	144
Time Adjustment and Synchronization	144
User Time Control Actions	145
System Time Control Actions	146
NTP Clock Synchronization	146
NTP Architecture	147
Global Positioning System (GPS)	148
SCADA System Components	149
Control Center – SCADA Manager	149
FEP	149
M-OPC	149
IP Gateway	151
Legacy ModBus FEP	151
Appendix A - ACE3600 Specifications	153
Power Supply Module Specifications	156
CPU 3610/CPU 3640 Module Specifications	159
DI Module Specifications	160
DO/DI FET Module Specifications	163
DO Relay Module Specifications	165
AI Module Specifications	167
AO Module Specifications	168
Mixed I/O Module Specifications	169
Mixed Analog Module Specifications	171
Expansion Power Supply Module Specifications	173
Expansion Module Specifications	174
Expansion LAN Switch Specifications	175
Appendix B - FCC InformationSpectrum and Regulatory Update	176
FCC Rules Update	176
Refarming and Narrow Banding	176
UHF Offset Channels	176
VHF Splinter Channels	177
Emission Designators	177
Data Efficiency Standards	177
Narrowbanding Update	178
Licensing of Fixed Data Systems	179
Spectrum Available for Fixed Data Systems	179
UHF Low Power Pool	179
Low Power Pool Group Specifications	180
Other Part 90 Frequency Options	181

Match case Limit results 1 per page

Communications

A number of connection methods are available when configuring an Ethernet-based

RTU:

Static IP address – The user sets the IP address within the configuration of the

device in the STS. To use this method, follow the instructions for configuring an

RTU in the Operation chapter in the ACE3600 STS User Guide. All DHCP

parameters will remain at default values.

DHCP-supplied reserved IP address – For every ACE3600 RTU, an IP address

will be reserved within the DHCP server. The link between the RTU and the

reservation will be based on unique ID. In the DHCP Server, set the unique ID.

The default unique is the MAC address. In the DHCP server, define a reservation

for a specific RTU based on its MAC address.

DHCP-supplied dynamic IP address – A dynamic IP address is distributed from

the DHCP server to the ACE3600 RTUs. The IP address of each ACE device is

unpredictable. In this case you will need a DNS server that will resolve the link

between the IP address and the RTU. You will have to supply a name for each

RTU. This name will be updated within the DNS server along with IP address of

the RTU. Within IP conversion table of ACE3600 RTU you will use this DNS

name instead of IP address.

In order to comply with IP networks standards, all configuration methods described in

this chapter are based on standard procedures used in IP networks.

MDLC over ASTRO IV&D

With SCADA systems, ACE3600 RTUs can be connected to an ASTRO IV&D radio.

The ASTRO infrastructure (R6.4 or higher) and radio must support integrated voice and

data (named IV&D). This is relevant to Motorola subscriber data radios such as the

XTL5000 mobile and XTS2500 portable.

The connection to ASTRO IV&D can be made via LAN or via radio. The LAN is called

a CEN (Customer Enterprise Network). An IP Gateway or RTU with an Ethernet port can

be connected to the CEN. On the other end, an RTU can be connected to an ASTRO

IV&D radio via an RS232 data cable. Note that a specific codeplug which supports the

data option must be used when programming them.

In the figure below, the SCADA central and IP Gateway are connected via LAN to a

Customer Enterprise Network (CEN). The CEN is connected via a border router gateway

to the ASTRO IV&D infrastructure. An RTU, running MDLC over IP protocol over PPP,

is connected via XTL5000 radio using an RS232 data cable. A unique IP address is

assigned by the GPRS Gateway Support Node (GGSN) to each RTU according to its

radio individual unit ID (UID), such that when a frame is transmitted from the CEN to

that IP address, the Packet Data Router (PDR) and Radio Network Gateway (RNG)

transmit it to the appropriate radio.

108