Motorola - Manual - PONTO A PONTO - PTP 600 ANTENA INTEGRADA E EXTERNA

PTP 600 Series
User Guide
MOTOROLA POINT-TO-POINT WIRELESS SOLUTIONS

MOTOROLA, Inc.
Point-to-Point Wireless Bridges – PTP 600 Series
Software Release PTP 600-08-xx
System User Guide
July 14th, 2009
Ref: PHN-0896-008v007
Copyright Information
This document is the confidential property of Motorola, Inc. and without its prior written consent may
not be copied or released to third parties.
MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein are trademarks
of Motorola, Inc. ® Reg. U.S. Pat & Tm. Office. PTP 600 is a trademark of Motorola, Inc. All other
product or service names are the property of their respective owners.
© 2006-2009 Motorola, Inc. All rights reserved.
http://www.motorola.com/ptp
Disclaimer
The parameters quoted in this document must be specifically confirmed in writing
before they become applicable to any particular order or contract. The company
reserves the right to make alterations or amendments to the detail specification at its
discretion. The publication of information in this document does not imply freedom
from patent or other rights of Motorola, Inc. or others.
Contents
Contents
1 About This User Guide.................................................................................................................... 1
1.1 Who Should Use This Guide.................................................................................................... 1
1.2 Contact Information .................................................................................................................. 2
1.3 Interpreting Typeface and Other Conventions ......................................................................... 2
1.3.1 Fonts .............................................................................................................................. 2
1.3.2 Terminology ................................................................................................................... 3
1.3.3 Warnings, Cautions and Notes ...................................................................................... 3
1.4 Getting Additional Help............................................................................................................. 4
1.5 Repair and Service................................................................................................................... 4
1.6 Warranty................................................................................................................................... 5
1.7 Electrical Safety........................................................................................................................ 5
1.8 RF Safety ................................................................................................................................. 7
1.8.1 RF Exposure Near the Antenna..................................................................................... 7
1.8.2 Limits and Guidelines for RF Exposure ......................................................................... 7
1.8.3 Power Density Exposure Limit ....................................................................................... 8
1.8.4 Calculated Distances and Power Compliance Margins ................................................. 8
1.9 Compliance with Regulations................................................................................................. 10
1.9.1 General ........................................................................................................................ 10
1.9.2 FCC and ETSI Compliance Testing............................................................................. 10
1.9.3 Radio and Television Interference ............................................................................... 11
1.9.4 Deployment and Operation .......................................................................................... 11
1.9.5 Examples of Regulatory Limits .................................................................................... 11
1.9.6 Registration of Links .................................................................................................... 12
2 Product Description ...................................................................................................................... 13
2.1 Product Function .................................................................................................................... 13
2.2 Typical Deployment................................................................................................................ 14
2.3 Frequency Variants ................................................................................................................ 15
2.4 Other Product Variants........................................................................................................... 16
2.5 Network Connection ............................................................................................................... 16
2.6 Outdoor Unit (ODU) ............................................................................................................... 17
2.7 PIDU Plus PTP 300/500/600 Series ...................................................................................... 18
2.7.1 Power and Ethernet LEDs ........................................................................................... 18
2.7.2 ODU, LAN and Recovery............................................................................................. 19
2.7.3 DC In and Out .............................................................................................................. 19
i
Contents
2.7.4 Remote Connectors and Jumpers ............................................................................... 19

2.7.5 Mains Connection ........................................................................................................ 20
2.8 Redundancy and Alternative Powering Configurations.......................................................... 21
2.9 Remote LEDs and Recovery Switch ...................................................................................... 23
2.10 Cables and Connectors.......................................................................................................... 23
2.11 PTP and Lightning Protection ................................................................................................ 24
2.12 Mounting Brackets.................................................................................................................. 25
3 Product Features ........................................................................................................................... 26
3.1 Ethernet Frames..................................................................................................................... 26
3.2 Management Function............................................................................................................ 27
3.3 Configuration and Management............................................................................................. 27
3.4 Channel Bandwidth and Link Symmetry Control ................................................................... 28
3.5 Non Line Of Sight (NLOS) and Line Of Sight (LOS) ............................................................. 28
3.6 Upgradeable Software............................................................................................................ 28
3.7 Networking Information .......................................................................................................... 28
3.8 Time Division Duplex (TDD) Synchronization ........................................................................ 29
3.8.1 Introduction .................................................................................................................. 29
3.8.2 TDD Synchronization ................................................................................................... 30
3.8.3 Implementation of TDD Synchronization ..................................................................... 31
3.8.4 System Constraints with TDD Synchronization Enabled ............................................. 31
3.9 Link Mode Optimization.......................................................................................................... 32
3.9.1 IP Link Mode Optimization ........................................................................................... 32
3.9.2 TDM Link Mode Optimization....................................................................................... 32
3.10 Telecoms Circuits................................................................................................................... 33
3.10.1 Lowest Telecoms Modulation Mode ............................................................................ 33
3.10.2 Fixed Frequency Operation ......................................................................................... 33
3.10.3 Further Reading ........................................................................................................... 34
3.11 Radar Avoidance.................................................................................................................... 34
4 Planning Considerations.............................................................................................................. 35
4.1 Spectrum Planning ................................................................................................................. 35
4.1.1 Regions Without Mandatory Radar Detection ............................................................. 35
4.1.2 Regions With Mandatory Radar Detection .................................................................. 36
4.2 Licenses and Region Codes .................................................................................................. 36
4.3 Radar Avoidance and Bandwidth Operation.......................................................................... 37
4.4 Variable Channel Bandwidth Operation ................................................................................. 38
4.5 Link Planning.......................................................................................................................... 39
ii
Contents
4.5.1 Range and Obstacles .................................................................................................. 39

4.5.2 PTP LINKPlanner......................................................................................................... 39
4.6 Site Selection Criteria............................................................................................................. 40
4.6.1 ODU Site Selection ...................................................................................................... 40
4.6.2 PIDU Plus Site Selection ............................................................................................. 40
4.7 Wind Loading ......................................................................................................................... 40
4.7.1 Calculation of Lateral Force ......................................................................................... 41
4.7.2 Capabilities of the PTP 600 Series Bridges................................................................. 42
4.7.3 Wind Speed Statistics .................................................................................................. 42
4.8 Path Loss Considerations ...................................................................................................... 43
4.8.1 Calculating Path Loss .................................................................................................. 43
4.8.2 Adaptive Modulation .................................................................................................... 43
4.9 System Threshold, Output Power and Link Loss................................................................... 44
5 Lightning Protection ..................................................................................................................... 45
5.1 Lightning Protection Zones .................................................................................................... 45
5.2 LPU Configuration Options .................................................................................................... 48
5.3 LPU Kit ................................................................................................................................... 50
5.4 LPU Installation Wiring ........................................................................................................... 51
5.5 LPU Installation Diagrams...................................................................................................... 52
5.5.1 Typical Mast or Tower Installation ............................................................................... 53
5.5.2 Typical Wall Installation ............................................................................................... 54
5.5.3 Mast or Tower Installation with E1/T1.......................................................................... 55
5.5.4 Wall Installation with E1/T1.......................................................................................... 56
5.5.5 Mast or Tower Installation with GPS Sync Unit ........................................................... 57
5.5.6 Wall Installation with GPS Sync Unit ........................................................................... 58
5.5.7 Mast or Tower Installation with GPS Sync Unit and E1/T1.......................................... 59
5.5.8 Wall Installation with GPS Sync Unit and E1/T1.......................................................... 60
6 Installation...................................................................................................................................... 61
6.1 Installation Support................................................................................................................. 62
6.2 Legal Disclaimer..................................................................................................................... 62
6.3 Preparation............................................................................................................................. 62
6.3.1 Checks ......................................................................................................................... 62
6.3.2 Tools Required............................................................................................................. 62
6.4 Mounting the ODUs................................................................................................................ 63
6.4.1 Mounting Bracket ......................................................................................................... 63
6.4.2 ODU Mounting Procedure............................................................................................ 64
iii
Contents
6.4.3 Hoist and Safety Loop.................................................................................................. 66

6.5 Connecting Up........................................................................................................................ 67
6.5.1 Preparing the PIDU Plus To ODU Cable ..................................................................... 67
6.5.2 Making the Connections at the ODU ........................................................................... 70
6.5.3 Making the PIDU Plus Connection At The ODU.......................................................... 71
6.5.4 Routing the Cable ........................................................................................................ 72
6.5.5 Fitting a Lightning Protection Unit ................................................................................ 72
6.5.6 Grounding the Installation............................................................................................ 73
6.5.7 Making the ODU Connection at the PIDU Plus ........................................................... 73
6.5.8 Making the Network Connection at the PIDU Plus ...................................................... 75
6.5.9 Mounting the PIDU Plus............................................................................................... 75
6.5.10 Powering Up................................................................................................................. 79
6.6 Establishing a Radio Link....................................................................................................... 80
6.6.1 Aligning the PTP 600 Series Bridge ODUs.................................................................. 80
6.6.2 Behaviour During Installation ....................................................................................... 81
6.6.3 Adjust Power Settings.................................................................................................. 82
6.6.4 Disarm on Completion ................................................................................................. 83
7 Web Page Reference ..................................................................................................................... 84
7.1 Menu Navigation Bar.............................................................................................................. 84
7.2 Home (System Summary)...................................................................................................... 86
7.2.1 Home Page Alarm Display........................................................................................... 87
7.2.2 System Alarms ............................................................................................................. 88
7.3 System Status ........................................................................................................................ 91
7.3.1 Histogram Data ............................................................................................................ 96
7.4 System Administration............................................................................................................ 97
7.5 Configuration .......................................................................................................................... 98
7.5.1 System Configuration................................................................................................... 98
7.5.2 QoS Configuration Page ............................................................................................ 100
7.5.3 LAN Configuration...................................................................................................... 103
7.5.4 Save and Restore ...................................................................................................... 107
7.5.5 Telecoms Configuration ............................................................................................. 112
7.6 Statistics ............................................................................................................................... 114
7.6.1 Detailed Counters ...................................................................................................... 117
7.7 Installation ............................................................................................................................ 120
7.7.1 Factory Configuration................................................................................................. 120
7.7.2 Manual Configuration................................................................................................. 121
iv
Contents
7.7.3 Current Installation Summary .................................................................................... 123

7.7.4 Installation Step 1 - Interface Configuration............................................................... 124
7.7.5 Installation Step 2 - Wireless Configuration............................................................... 128
7.7.6 Installation Step 3 - Confirm Configuration ................................................................ 133
7.7.7 Disarm Installation...................................................................................................... 135
7.7.8 Graphical Install ......................................................................................................... 137
7.8 Software Upgrade ................................................................................................................ 138
7.8.1 Locate and Upload Software Image........................................................................... 139
7.8.2 Program Software Image into Memory ...................................................................... 140
7.8.3 Software Upgrade Complete...................................................................................... 141
7.8.4 Reboot After Software Upgrade................................................................................. 141
7.9 Spectrum Management........................................................................................................ 143
7.9.1 Wireless Channels ..................................................................................................... 143
7.9.2 Spectrum Management Measurements..................................................................... 143
7.9.3 Measurement Analysis............................................................................................... 143
7.9.4 The Spectrum Management Master / Slave Relationship ......................................... 144
7.9.5 Spectrum Management Configuration ....................................................................... 148
7.9.6 Barring Channels ....................................................................................................... 149
7.9.7 Master and Slave Channel Spectrum Graphics......................................................... 149
7.9.8 Active Channel History............................................................................................... 151
7.9.9 Viewing Historic Spectrum Management Metrics ...................................................... 152
7.9.10 Spectrum Management (Fixed Frequency) ............................................................... 153
7.9.11 Spectrum Management Control with Radar Avoidance............................................. 155
7.9.12 PTP 25600 Spectrum Management Example ........................................................... 157
7.10 Remote Management........................................................................................................... 158
7.10.1 Control Access to HTTP Interface ............................................................................. 159
7.10.2 Control Access to Telnet Interface............................................................................. 159
7.10.3 SNMP (Simple Network Management Protocol)........................................................ 159
7.10.4 Supported Management Information Bases (MIBS) .................................................. 159
7.10.5 Diagnostics Alarms .................................................................................................... 161
7.10.6 SNMP Configuration .................................................................................................. 162
7.10.7 SMTP (Simple Mail Transport Protocol) .................................................................... 162
7.10.8 SNTP (Simple Network Time Protocol) ..................................................................... 163
7.10.9 Setting the clock......................................................................................................... 163
7.11 Diagnostics Plotter ............................................................................................................... 164
7.11.1 Diagnostic Plotter Page ............................................................................................. 165
v
Contents
7.11.2 CSV Download........................................................................................................... 166

7.12 Change Password ................................................................................................................ 167
7.13 License Key.......................................................................................................................... 167
7.14 Properties ............................................................................................................................. 169
7.15 Reboot.................................................................................................................................. 170
8 Recovery Mode ............................................................................................................................ 171
8.1 Entering Recovery Mode...................................................................................................... 171
8.2 Upgrade Software Image ..................................................................................................... 173
8.3 Reset IP & Ethernet Configuration ....................................................................................... 175
8.4 Erase Configuration.............................................................................................................. 176
8.5 Reboot.................................................................................................................................. 179
9 Troubleshooting .......................................................................................................................... 180
9.1 Test Link End Hardware....................................................................................................... 180
9.1.1 Power LED is Off........................................................................................................ 182
9.1.2 Power LED is Flashing............................................................................................... 183
9.1.3 Ethernet LED did not Flash 10 Times ........................................................................ 183
9.1.4 No Ethernet Activity ................................................................................................... 184
9.1.5 Irregular Ethernet Activity........................................................................................... 185
9.1.6 Connection is not 1000 BaseT................................................................................... 185
9.1.7 Test RJ45 Resistance................................................................................................ 185
9.1.8 Test GPS Synchronization Unit ................................................................................. 187
9.2 Test Radio Link .................................................................................................................... 188
9.2.1 No Activity .................................................................................................................. 188
9.2.2 Some Activity ............................................................................................................. 189
9.3 Lightning Strike..................................................................................................................... 189
10 Connectorized PTP 600 Series Bridge ...................................................................................... 190
10.1 Product Description .............................................................................................................. 190
10.1.1 Hardware.................................................................................................................... 190
10.1.2 Antenna...................................................................................................................... 191
10.2 Software/Features ................................................................................................................ 191
10.2.1 Status Page................................................................................................................ 191
10.2.2 Configuration Pages .................................................................................................. 192
10.2.3 Installation Pages....................................................................................................... 193
10.3 Deployment Considerations ................................................................................................. 197
10.4 Link Budget .......................................................................................................................... 197
10.5 Regulatory Issues with Connectorized Units ....................................................................... 197
vi
Contents
10.5.1 Cable Losses (FCC Regions Only)............................................................................ 198

10.6 Antenna Choices .................................................................................................................. 198
10.7 Installation ............................................................................................................................ 199
10.7.1 Cables and Connectors ............................................................................................. 199
10.7.2 Tools .......................................................................................................................... 199
10.7.3 Miscellaneous supplies .............................................................................................. 200
10.7.4 Mounting the Connectorized 600 Series Bridge ........................................................ 200
10.7.5 Mounting the antennas .............................................................................................. 200
10.7.6 Alignment Process ..................................................................................................... 201
10.7.7 Aligning Dual Polar Antennas .................................................................................... 201
10.7.8 Aligning Separate Antennas ...................................................................................... 201
10.7.9 Completing the Installation......................................................................................... 202
10.7.10 Antenna Cable Fixing................................................................................................. 202
10.7.11 Antenna Connection Weatherproofing....................................................................... 203
10.8 Additional Lightning Protection............................................................................................. 204
10.8.1 ODU Mounted Outdoors ............................................................................................ 204
10.8.2 ODU Mounted Indoors ............................................................................................... 205
11 TDD Synchronization Installation and Configuration.............................................................. 206
11.1 Benefits of TDD Synchronization ......................................................................................... 206
11.2 TDD Synchronization Installation ......................................................................................... 207
11.2.1 Recommended Kit ..................................................................................................... 207
11.2.2 GPS Sync Unit Connections ...................................................................................... 208
11.2.3 Complete GPS Sync Unit Installation ........................................................................ 209
11.3 TDD Synchronization Configuration..................................................................................... 210
11.3.1 TDD Synchronization Enable..................................................................................... 210
11.3.2 TDD Synchronization Configuration........................................................................... 211
11.3.3 Confirm Settings and Reboot ODU............................................................................ 213
11.3.4 TDD Synchronization Status...................................................................................... 214
11.3.5 Disarm ODU Following TDD Sync Configuration ...................................................... 216
12 E1/T1 Installation Guide.............................................................................................................. 217
12.1 E1/T1 Connection Diagrams ................................................................................................ 217
12.1.1 T568B Color Coding .................................................................................................. 217
12.1.2 Connections at the ODU and Patch Panel ................................................................ 218
12.1.3 Balancing Signals ...................................................................................................... 220
12.2 Connecting the E1/T1 Cable to the ODU ............................................................................. 221
12.3 Disconnecting the E1/T1 Cable............................................................................................ 223
vii
Contents
12.4 Routing the Cable................................................................................................................. 223

12.5 Customer Cable Termination ............................................................................................... 223
12.6 Lightning Protection and E1/T1............................................................................................ 224
12.6.1 Overview .................................................................................................................... 224
12.6.2 Recommended Additional Components for E1/T1 Installation. ................................. 224
12.7 Testing the E1/T1 Installation............................................................................................... 225
12.7.1 Pre-Power Testing ..................................................................................................... 225
13 Data Rate Calculations................................................................................................................ 226
13.1 Data Rate Defined................................................................................................................ 226
13.2 Calculation Procedure and Example.................................................................................... 226
13.2.1 Procedure................................................................................................................... 226
13.2.2 Example ..................................................................................................................... 227
13.3 Data Throughput Capacity ................................................................................................... 228
13.4 Range Adjustment Curves ................................................................................................... 239
14 AES Encryption ........................................................................................................................... 248
14.1 Encryption Standard Used ................................................................................................... 248
14.2 Upgrading for Link Encryption.............................................................................................. 248
14.3 Configuring Link Encryption ................................................................................................. 248
14.3.1 License Keys.............................................................................................................. 249
14.3.2 Encryption Mode and Key.......................................................................................... 250
14.4 Wireless Link Encryption FAQ ............................................................................................. 252
14.4.1 Encryption data entry fields are not available ............................................................ 252
14.4.2 Link fails to bridge packets after enabling link encryption ......................................... 252
14.4.3 Loss of AES following downgrade ............................................................................. 252
15 Remote Software Upgrade by TFTP .......................................................................................... 253
16 Legal Notices ............................................................................................................................... 255
16.1 Motorola Inc. End User License Agreement ........................................................................ 255
16.1.1 Definitions .................................................................................................................. 255
16.1.2 Grant of License......................................................................................................... 256
16.1.3 Conditions of Use....................................................................................................... 256
16.1.4 Title; Restrictions........................................................................................................ 258
16.1.5 Confidentiality............................................................................................................. 258
16.1.6 Right to Use Motorola’s Name ................................................................................... 259
16.1.7 Transfer...................................................................................................................... 259
16.1.8 Updates...................................................................................................................... 259
16.1.9 Maintenance............................................................................................................... 260
viii
Contents
16.1.10 Disclaimer .................................................................................................................. 260

16.1.11 Limitation of Liability................................................................................................... 260
16.1.12 U.S. Government ....................................................................................................... 261
16.1.13 Term of License ......................................................................................................... 261
16.1.14 Governing Law ........................................................................................................... 261
16.1.15 Assignment ................................................................................................................ 261
16.1.16 Survival of Provisions................................................................................................. 262
16.1.17 Entire Agreement ....................................................................................................... 262
16.1.18 Third Party Software .................................................................................................. 262
16.2 Hardware Warranty in U.S. .................................................................................................. 264
16.3 Limit of Liability..................................................................................................................... 264
17 PTP 600 Reference Information ................................................................................................. 265
17.1 PTP 600 General Reference Information............................................................................. 265
17.1.1 PTP 600 System Specifications................................................................................. 265
17.1.2 PTP 600 Safety Compliance...................................................................................... 267
17.1.3 PTP 600 EMC Immunity Compliance ........................................................................ 268
17.1.4 PTP 600 Environmental Specifications...................................................................... 269
17.2 PTP 25600 Reference Information....................................................................................... 270
17.2.1 PTP 25600 Examples of Regulatory Limits ............................................................... 270
17.2.2 PTP 25600 Licenses and Region Codes................................................................... 271
17.2.3 PTP 25600 Regulatory Compliance........................................................................... 272
17.2.4 PTP 25600 Radio System Specifications .................................................................. 273
17.2.5 PTP 25600 Emissions and Radio Certifications ........................................................ 274
17.2.6 PTP 25600 Available Spectrum Settings................................................................... 274
17.2.7 PTP 25600 System Threshold, Output Power and Link Loss ................................... 277
ix
Contents

17.6.8 PTP 54600 FCC Antenna Restrictions ...................................................................... 312
17.7.8 PTP 58600 FCC Antenna Restrictions ...................................................................... 329
x
Contents
18 FAQs ............................................................................................................................................. 341

19 Glossary ....................................................................................................................................... 343
Index ....................................................................................................................................................... I
xi
List of Figures
List of Figures
Figure 1 - Typical PTP 600 Series Bridge Deployment........................................................................ 14
Figure 2 - Mod Record Label................................................................................................................ 16
Figure 3 – PTP 600 Series Bridge Outdoor Unit (ODU) with PTP-LPU ............................................... 17
Figure 4 - Power Indoor Unit (PIDU Plus PTP 300/500/600 Series).................................................... 18
Figure 5 – PIDU Plus Recovery Switch Location ................................................................................. 19
Figure 6 – PIDU Plus Power Input........................................................................................................ 20
Figure 7 – Relationship Between DC Voltage and Cable Length ........................................................ 21
Figure 8 - External DC Supply Only ..................................................................................................... 22
Figure 9 - External DC Supply and AC Supply..................................................................................... 22
Figure 10 - External DC Supply and Redundant AC Supply ................................................................ 22
Figure 11 - Remote LED and Recovery Switch Wiring ........................................................................ 23
Figure 12 – PTP 600 Series Bridge Layer Diagram ............................................................................. 27
Figure 13 - Co-location of Links Interference Problem - A Simple Example ........................................ 29
Figure 14 - TDD Synchronization And Co location Example................................................................ 30
Figure 15 - 5.8 GHz UK RTTT Channel Avoidance – 30 MHz Channel Bandwidth (Example) ........... 37
Figure 16 - ODU mounted in Zones A & B ........................................................................................... 46
Figure 17 – Using a Finial to extend Zone B ........................................................................................ 46
Figure 18 – Example of PTP-LPU Configuration – Option 1 (Back-to-Back Recommended) ............. 48
Figure 19 - PTP-LPU - Installation Option 2 (Using U-Bolt) ................................................................. 49
Figure 20 - PTP LPU Full Kit ................................................................................................................ 50
Figure 21 - Simplified Circuit Diagram.................................................................................................. 51
Figure 22 - Typical Mast or Tower Installation ..................................................................................... 53
Figure 23 - Typical Wall Installation...................................................................................................... 54
Figure 24 – Mast or Tower Installation with E1/T1 ............................................................................... 55
Figure 25 - Wall Installation with E1/T1 ................................................................................................ 56
Figure 26 – Mast or Tower Installation with GPS Sync Unit................................................................. 57
xii
List of Figures
Figure 27 –Wall Installation with GPS Sync Unit.................................................................................. 58
Figure 28 - Mast or Tower Installation with GPS Sync Unit and E1/T1................................................ 59
Figure 29 - Wall Installation with GPS Sync Unit and E1/T1................................................................ 60
Figure 30 – ODU with Mounting Bracket and Earth Bonding Leads .................................................... 63
Figure 31 – ODU Bracket Strap............................................................................................................ 64
Figure 32 – ODU Mounting Bracket ..................................................................................................... 64
Figure 33 - ODU Mounted on Pole ....................................................................................................... 65
Figure 34 - Integral Safety Loop ........................................................................................................... 66
Figure 35 - Correct Cable Preparation for the Recommended Cable .................................................. 68
Figure 36 - Completed ODU Connector ............................................................................................... 69
Figure 37 - Correct and Incorrect Tightening of Cable Gland .............................................................. 69
Figure 38 – ODU PIDU Plus Connexion............................................................................................... 70
Figure 39 - Connecting the PIDU Plus+ to the ODU ............................................................................ 71
Figure 40 - Disconnecting the ODU...................................................................................................... 72
Figure 41 - Connecting the ODU to the PIDU Plus+ ............................................................................ 74
Figure 42 - Making the Network Connection at the PIDU Plus ............................................................ 75
Figure 43 - Mounting the PIDU Plus..................................................................................................... 76
Figure 44 - Correct and Incorrect RJ45 Cable Dressing ...................................................................... 77
Figure 45 – PIDU Plus Drip Loop Configuration................................................................................... 78
Figure 46 - Menu Navigation Bar.......................................................................................................... 85
Figure 47 - System Summary Page ..................................................................................................... 86
Figure 48 - Alarm Warning Triangle ..................................................................................................... 87
Figure 49 - Status Page........................................................................................................................ 91
Figure 50 - System Administration Login Page .................................................................................... 97
Figure 51 - System Configuration Page ............................................................................................... 99
Figure 52 - QoS Configuration Page .................................................................................................. 100
Figure 53 - LAN Configuration Page .................................................................................................. 103
xiii
List of Figures
Figure 54 - Configuration Reboot Page.............................................................................................. 105
Figure 55 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled .................................. 105
Figure 56 - VLAN Configuration Fields............................................................................................... 106
Figure 57 - LAN Configuration Page - Manual Ethernet Configuration .............................................. 107
Figure 58 - Save and Restore Configuration Page ............................................................................ 108
Figure 59 - Save Configuration File Screen ....................................................................................... 109
Figure 60 – PTP 600 Example Configuration File .............................................................................. 109
Figure 61 - Restore Configuration File Pop Up Screen...................................................................... 110
Figure 62 - Reset Configuration and Reboot Confirmation Pop-up ................................................... 111
Figure 63 - Telecoms Data Entry........................................................................................................ 112
Figure 64 - System Statistics Page .................................................................................................... 114
Figure 65 - Detailed Counters Page ................................................................................................... 117
Figure 66 - License Key Data Entry.................................................................................................... 122
Figure 67 – Current Installation Summary.......................................................................................... 123
Figure 68 - Installation Interface Configuration .................................................................................. 124
Figure 69 - VLAN Warning ................................................................................................................. 125
Figure 70 - Telecoms Configuration Interface .................................................................................... 126
Figure 71 –Wireless Configuration ..................................................................................................... 128
Figure 72 – Fixed Frequency Configuration Example ........................................................................ 132
Figure 73 – Confirm Installation Configuration ................................................................................... 133
Figure 74 - Reboot Confirmation Pop Up ........................................................................................... 134
Figure 75 – Disarm Installation........................................................................................................... 135
Figure 76 - Optional Post Disarm Configuration 1.............................................................................. 136
Figure 77 - Optional Post Disarm Configuration 2.............................................................................. 136
Figure 78 – Graphical Installation Screen .......................................................................................... 137
Figure 79 - Software Upgrade ............................................................................................................ 138
Figure 80 - Software Upgrade Image Check...................................................................................... 140
xiv
List of Figures
Figure 81 - Software Download Progress Indicator............................................................................ 141
Figure 82 - Software Upgrade Complete Page ................................................................................. 141
Figure 83 - Reboot Confirmation Pop Up ........................................................................................... 141
Figure 84 - Spectrum Management as seen from the Master............................................................ 146
Figure 85 - Spectrum Management as seen from the Slave.............................................................. 147
Figure 86 - Example Spectrum Management Graphic ....................................................................... 149
Figure 87 - Active Channel History Screen ........................................................................................ 151
Figure 88 - Spectrum Management Time Series Plot ........................................................................ 152
Figure 89 - Spectrum Management Fixed Frequency Screen ........................................................... 153
Figure 90 - Spectrum Management Help Page (Fixed Frequency) ................................................... 154
Figure 91 - Spectrum Management Master Screen With Operational Restrictions ........................... 155
Figure 92 - Spectrum Management Slave Screen With Operational Restrictions ............................. 156
Figure 93 - PTP 25600 Example of Spectrum Management Page .................................................... 157
Figure 94 - Remote Management....................................................................................................... 158
Figure 95 – Warning when disabling HTTP interface......................................................................... 160
Figure 96 - Remote Management - Diagnostic Alarms ...................................................................... 161
Figure 97 - Diagnostic Plotter ............................................................................................................. 165
Figure 98 - CSV Download................................................................................................................. 166
Figure 99 - Password Change............................................................................................................ 167
Figure 100 - Software License Key Data Entry .................................................................................. 167
Figure 101 - License Key reboot Screen ............................................................................................ 168
Figure 102 - Reboot Confirmation Pop Up ......................................................................................... 168
Figure 103 – Properties ...................................................................................................................... 169
Figure 104 - System Reboot............................................................................................................... 170
Figure 106 - Recovery Mode Warning Page ...................................................................................... 171
Figure 107 - Recovery Options Page ................................................................................................. 172
xv
List of Figures
Figure 108 - Software Download Progress Indicator Page ................................................................ 173
Figure 109 - Software Download Complete Page .............................................................................. 173
Figure 111 - Confirm Reset to Factory Default Pop Up...................................................................... 175
Figure 112 - IP and Ethernet Erased Successfully page.................................................................... 175
Figure 114 - Confirm Erase Configuration Pop Up............................................................................. 176
Figure 115 - Erase Configuration Successful Page ........................................................................... 177
Figure 116 – Erase Configuration - Reboot Confirmation Pop Up ..................................................... 178
Figure 117 – Recovery - Reboot Confirmation Pop Up...................................................................... 179
Figure 118 – Link End Hardware Test Flowchart ............................................................................... 181
Figure 119 - PTP LPU Test Points ..................................................................................................... 184
Figure 120 - GPS Synchronization Unit.............................................................................................. 187
Figure 121 – Connectorized 600 Series Bridge Outdoor Unit............................................................ 191
Figure 122 - Connectorized 600 Series bridge Status Page .............................................................. 192
Figure 123 - Connectorized 600 Series bridge ‘System Configuration’ Page .................................... 192
Figure 124 - Connectorized PTP 600 Series Bridge ‘Installation’ Page............................................. 193
Figure 125 - Connectorized 600 Series bridge ‘Confirm Installation’ Page........................................ 195
Figure 126 - Connectorized 600 Series bridge ‘Disarm Installation’ Page......................................... 196
Figure 127 - Forming a Drip Loop ...................................................................................................... 203
Figure 128 - Weatherproofing the Antenna Connections ................................................................... 203
Figure 129- Additional Grounding When Using Connectorized Units ................................................ 204
Figure 130 - Lightning Arrestor Mounting ........................................................................................... 205
Figure 131 - Polyphaser Assembly..................................................................................................... 205
Figure 132 - GPS Synchronization Unit.............................................................................................. 207
Figure 133 - GPS Synchronization Unit Connections ........................................................................ 208
Figure 134 - TDD Sync - PTP600 Deployment Diagram.................................................................... 208
xvi
List of Figures
Figure 135- GPS Synchronization Unit Complete Installation............................................................ 209
Figure 136 - Enabling TDD Synchronization Feature......................................................................... 210
Figure 137 - Configure TDD Synchronization .................................................................................... 211
Figure 138 - Confirm TDD Synchronization Configuration Parameters ............................................. 213
Figure 139 - Status Page - TDD Enabled and Synchronized............................................................. 214
Figure 140 - Status Page - TDD Enabled and Not Synchronized ..................................................... 215
Figure 141 - Disarm Following TDD Synchronization ........................................................................ 216
Figure 142 - RJ45 Pin Connection (T568B Color Coding) ................................................................. 217
Figure 143 - Cable Connection Diagram (T568B Color Coding)........................................................ 218
Figure 144 - E1-T1 Connections at the ODU and Patch Panel.......................................................... 219
Figure 145 - Two E1-T1-120 Ohms signal Balanced to PTP600 Interface ........................................ 220
Figure 146 - PIDU Plus and E1-T1 Connexion .................................................................................. 221
Figure 147 - Connecting the E1/T1 to the ODU ................................................................................. 222
Figure 148 - Disconnecting the ODU.................................................................................................. 223
Figure 149 - Example of a Balun ........................................................................................................ 223
Figure 150 – PTP 600 Range Adjustment for Data Rates, Curve A .................................................. 241
Figure 151 – PTP 600 Range Adjustment for Data Rates, Curve B .................................................. 241
Figure 152 – PTP 600 Range Adjustment for Data Rates, Curve C .................................................. 242
Figure 153 – PTP 600 Range Adjustment for Data Rates, Curve D .................................................. 242
Figure 154 – PTP 600 Range Adjustment for Data Rates, Curve E .................................................. 243
Figure 155 – PTP 600 Range Adjustment for Data Rates, Curve F .................................................. 243
Figure 156 – PTP 600 Range Adjustment for Data Rates, Curve G.................................................. 244
Figure 157 – PTP 600 Range Adjustment for Data Rates, Curve H .................................................. 244
Figure 158 – PTP 600 Range Adjustment for Data Rates, Curve K .................................................. 245
Figure 159 – PTP 600 Range Adjustment for Data Rates, Curve L................................................... 245
Figure 160 – PTP 600 Range Adjustment for Data Rates, Curve N .................................................. 246
Figure 161 – PTP 600 Range Adjustment for Data Rates, Curve O.................................................. 247
xvii
List of Figures
Figure 162 – AES Software License Key Data Entry ......................................................................... 249
Figure 163 – AES Configuration Data Entry Page ............................................................................. 251
Figure 164 - Configuration Reboot Screen......................................................................................... 252
Figure 165 - 2.5 GHz BRS Band Channel Assignments .................................................................... 276
Figure 166 – PTP 45600 Available Spectrum in the 30 MHz Channel Bandwidth (RC 23)............... 282
Figure 170 – PTP 45600 Available Spectrum in the 5 MHz Channel Bandwidth (RC 23)................. 284
Figure 173 – PTP 48600 Available Spectrum in the 20 MHz Channel Bandwidth (RC 15 and 23)... 290
Figure 176 – PTP 48600 Available Spectrum in the 5 MHz Channel Bandwidth (RC 15 and 23)..... 292
Figure 179 – PTP 49600 Available Spectrum in the 20 MHz Channel Bandwidth ............................ 298
Figure 181 – PTP 49600 Available Spectrum in the 5 MHz Channel Bandwidth............................... 299
xviii
List of Figures
xix
List of Tables
List of Tables
Table 1 - Contact Information ................................................................................................................. 2
Table 2 - Font types................................................................................................................................ 2
Table 3 - Power Compliance Margins .................................................................................................... 9
Table 4 - PTP 600 Series Bridge Frequency Variants ......................................................................... 15
Table 5 - Lateral Force – Imperial ........................................................................................................ 41
Table 6 - Lateral Force – Metric ........................................................................................................... 41
Table 7 - Audio indications from the ODU ............................................................................................ 80
Table 8 – Telecoms Channel Status Alarm Conditions........................................................................ 88
Table 9 – QoS Default Settings .......................................................................................................... 101
Table 10 – Classification rules upgrade example............................................................................... 101
Table 11 – IEEE802.1Q Classification rules ...................................................................................... 102
Table 12 – 600 Series Bridge Factory Configuration Values ............................................................. 120
Table 13 - Spectrum Management change state key......................................................................... 150
Table 14 - Spectrum Management Time Series Key ......................................................................... 152
Table 15 - Spectrum Management Change State Key With Operational Restrictions....................... 156
Table 16 - Resistance Table Referenced To The RJ45 at the PIDU Plus+ ....................................... 186
Table 17 - Cable Losses per Length .................................................................................................. 198
Table 18 - Telecoms Connection Pin Out........................................................................................... 218
Table 19 - Protection Requirements................................................................................................... 224
Table 20 - Resistance Table Referenced To the E1/T1 Source ........................................................ 225
Table 21 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = IP ........... 229
Table 22 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = TDM....... 231
Table 23 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = IP ........... 233
Table 24 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = TDM....... 235
Table 25 – Data Throughput for PTP 600 Full, Link Symmetry = Adaptive, Link Optimization = IP .. 237
Table 26 – Range Adjustment Characteristics ................................................................................... 239
xx
List of Tables
Table 27 – PTP 600 Management Specifications .............................................................................. 265
Table 28 – PTP 600 Ethernet Bridging Specifications ....................................................................... 266
Table 29 – PTP 600 Physical Specifications...................................................................................... 266
Table 30 – PTP 600 Power Supply Specifications ............................................................................. 267
Table 31 – PTP 600 Telecoms Interface Specifications..................................................................... 267
Table 32 – PTP 600 Safety Compliance Specifications ..................................................................... 267
Table 33 – PTP 600 EMC Immunity Compliance Specifications ....................................................... 268
Table 34 – PTP 600 Environmental Specifications ............................................................................ 269
Table 35 – PTP 25600 Examples of Regulatory Limits...................................................................... 270
Table 36 – PTP 25600 Licenses and Region Codes ......................................................................... 271
Table 37 - PTP 25600 RF Specifications ........................................................................................... 273
Table 38 - PTP 25600 EMC Emissions Compliance.......................................................................... 274
Table 39 - PTP 25600 Radio Certifications ........................................................................................ 274
Table 40 - PTP 25600 Channel Plan - FCC BRS-EBS Post-Transition Band ................................... 275
Table 41 – PTP 25600 - IP Mode - Threshold, Power and Loss per Modulation Mode..................... 277
Table 42 – PTP 25600 - TDM Mode - Threshold, Power and Loss per Modulation Mode ................ 278
Table 48 - PTP 45600 - IP Mode - Threshold, Power and Loss per Modulation Mode ..................... 285
Table 49 - PTP 45600 - TDM Mode - Threshold, Power and Loss per Modulation Mode ................. 286
xxi
List of Tables
Table 69 – PTP 54600 - IP Mode - Threshold, Power and Loss per Modulation Mode..................... 310
Table 70 – PTP 54600 - TDM Mode - Threshold, Power and Loss per Modulation Mode ................ 311
Table 71 - Allowed Antennas for Deployment in USA/Canada – 5.4 GHz......................................... 312
Table 77 – PTP 58600 Band Edge Tx Power Reduction ................................................................... 326
Table 78 - PTP 58600 - IP Mode - Threshold, Power and Loss per Modulation Mode .................... 327
Table 79 - PTP 58600 - TDM Mode - Threshold, Power and Loss per Modulation Mode ................ 328
Table 80 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz......................................... 329
xxii
List of Tables
Table 84 - PTP 59600 - IP Mode - Threshold, Power and Loss per Modulation Mode .................... 339
Table 85 - PTP 59600 - TDM Mode - Threshold, Power and Loss per Modulation Mode ................ 340
xxiii
List of Equations
List of Equations
Equation 1 - Peak power density in the far field ..................................................................................... 8
Equation 2 - Path Loss ......................................................................................................................... 43
Equation 3 - Link Loss .......................................................................................................................... 94
xxiv
1 About This User Guide
This guide describes the installation, commissioning, operation and fault finding of the
Motorola PTP 600 Series of Point-to-Point Wireless Ethernet Bridges. It contains the following
main sections:
• 2 Product Description
• 3 Product Features
• 4 Planning Considerations
• 5 Lightning Protection
• 6 Installation
• 7 Web Page Reference
• 8 Recovery Mode
• 9 Troubleshooting
• 10 Connectorized PTP 600 Series Bridge
• 11 TDD Synchronization Installation and Configuration
• 12 E1/T1 Installation Guide
• 13 Data Rate Calculations
• 14 AES Encryption
• 15 Remote Software Upgrade by TFTP
• 16 Legal Notices
• 17 PTP 600 Reference Information
1.1 Who Should Use This Guide

The guide is for use by the system installer and the end user IT professional. The system
installer will require expertise in the following areas:
• Outdoor radio equipment installation
• Network configuration
• Use of web browser for system configuration, monitoring and fault finding
1
1.2 Contact Information

Table 1 - Contact Information
Motorola, Inc.
Unit A1, Linhay Business Park,
Eastern Road,
Postal Address:
Ashburton,
Devon. TQ13 7UP
United Kingdom
Web Site: http://www.motorola.com/ptp
Sales Enquiries: [email protected]
Web Support: http://www.motorola.com/ptp/support
Email Support: [email protected]
All Other Enquiries: [email protected]
Telephone Enquiries and Global +1 (0) 877 515 0400 (Toll Free in the USA) and
Support: +44 (0) 808 234 4640 (Toll Free in the UK).
We welcome your feedback on the PTP 600 Series Bridge system documentation. This
includes feedback on the structure, content, accuracy, or completeness of our documents,
and any other comments you have. Send feedback to [email protected].
1.3 Interpreting Typeface and Other Conventions
1.3.1 Fonts
Motorola PTP system documents employ distinctive fonts to indicate the type of information,
as described in Table 2.
Table 2 - Font types

Font Type of Information
variable width bold Selectable option in a graphical user interface or
settable parameter in a web-based interface.
constant width regular Literal system response in a command-line interface.
constant width italic Variable system response in a command-line interface.
constant width bold Literal user input in a command-line interface.
constant width bold Variable user input in a command-line interface.
italic
2
1.3.2 Terminology
Motorola PTP system documents employ specific imperative terminology as follows:

• ‘Type’ means press the following characters.
• ‘Enter’ means type the following characters and then press Enter.
• ‘Highlight’ means click anywhere in a row of data to highlight the entire row.
• ‘Select’ means use the mouse to click on or branch to the menu item that follows.
1.3.3 Warnings, Cautions and Notes
The following describes how warnings, cautions and notes are used in Motorola PTP system
documents.
1.3.3.1 Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
1.3.3.2 Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
1.3.3.3 Notes
A note means that there is a possibility of an undesirable situation or provides additional

information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
3
1.4 Getting Additional Help

To get information or assistance as soon as possible for problems that you encounter, follow
this procedure:
1. Search this document, the user manuals that support the modules, and the software
release notes of supported releases:
i. In the Table of Contents for the topic.
ii. In the Adobe Reader® search capability for keywords that apply (Reader is a
registered trademark of Adobe Systems, Incorporated).
2. Visit the Motorola website at www.motorola.com/ptp
3. Ask your Motorola products supplier to help.
4. Gather information from affected units such as:

i. the IP addresses and MAC addresses
ii. the software releases
iii. the configuration of software features
iv. any available diagnostic downloads
5. Escalate the problem to Motorola Technical Support as follows. You may either:
i. Send e-mail to [email protected]
ii. Call our 24x7 Technical Support Center on +1 (0) 877 515 0400 (Worldwide)
or +44 (0) 808 234 4640 (UK Customers).
For warranty assistance, contact your reseller or distributor for the process.
1.5 Repair and Service

For unit repair or service, contact your service provider or an authorized Motorola Point-to-
Point Distributor for Return Material Authorization (RMA) and shipping instructions.
Alternatively, contact the PTP Global Technical Support Center to process an RMA.
4
1.6 Warranty
Motorola’s standard hardware warranty is for one (1) year from date of shipment from
Motorola or a Motorola Point-to-Point Distributor. Motorola warrants that hardware will
conform to the current relevant published specifications and will be free from material defects
in material and workmanship under normal use and service. Motorola shall within this time, at
its own option, either repair or replace the defective product within thirty (30) days of receipt
of the defective product. Repaired or replaced product will be subject to the original warranty
period but not less than thirty (30) days.
Motorola warranty for software is described in details in Section 16.1 Motorola Inc. End User
License Agreement.
1.7 Electrical Safety
WARNING
To prevent loss of life or physical injury, observe the safety guidelines in this section.
Power lines: Use extreme care when installing antennas near power lines.
Working at heights: Use extreme care when working at heights.
Grounding: The Outdoor Unit (ODU) for the PTP 600 Series Bridge must be properly
grounded to protect against lightning. In the USA and Canada it is the user’s responsibility to
install the equipment in accordance with Section 810 of the National Electric Code,
ANSI/NFPA No.70-1984 or Section 54 of the Canadian Electrical Code. These codes
describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire and
discharge unit, size of grounding conductors and connection requirements for grounding
electrodes. Other regulations may apply in different countries and therefore it is
recommended that installation of the outdoor unit be contracted to a professional installer.
Protective earth: The ODU for the PTP 600 Series Bridge must be grounded to a Protective
Earth in accordance with the Local Electrical Regulations.
PIDU Plus: It is recommended that the supplied Power Indoor Plus (PIDU Plus PTP
300/500/600 Series) is used to power the PTP 600 Series Bridge ODU. The use of other
power sources may invalidate safety approval and affect your warranty.
5
Cable measuring card: A cable measuring card must NEVER be used at the ODU end
connected to power from the PIDU Plus. It must only be used at the bottom of the mast with
a multimeter. This is because the PIDU Plus voltage exceeds the limit allowed in some
countries for safe handling in wet conditions and therefore may create a safety hazard.
Alternative DC supplies: When using alternative DC supplies (via the PIDU Plus DC in
terminals as described in Section 2.8 Redundancy and Alternative Powering Configurations),
such as battery-backed DC power source, the supply MUST comply with the following
requirements:
• The voltage and polarity is correct and is applied to the correct terminals in the PIDU Plus
• The power source is rated as SELV
• The power source is rated to supply at least 1A continuously
• The power source cannot provide more than the Energy Hazard Limit as defined by
IEC/EN/UL6090, Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA)
Primary disconnect device: The main power supply is the primary disconnect device.
External cables: Safety will be compromised if external quality cables are not used for
connections that will be exposed to the weather.
Non-Motorola power supply: Safety will be compromised if a different power supply is used
than the one supplied by Motorola as part of the system.
6
1.8 RF Safety
WARNING
To protect from overexposure to RF energy, observe the safety guidelines in this
section.
1.8.1 RF Exposure Near the Antenna
Minimum separation distance: Install the radios for the PTP 600 family of PTP wireless
solutions so as to provide and maintain the minimum separation distances from all persons.
The minimum separation distances for each frequency variant are specified in Section 1.8.4
Calculated Distances and Power Compliance Margins.
Avoid standing in front of the antenna: When the system is operational, avoid standing
directly in front of the antenna. Strong RF fields are present when the transmitter is on. The
Outdoor Unit (ODU) must not be deployed in a location where it is possible for people to
stand or walk inadvertently in front of the antenna.
1.8.2 Limits and Guidelines for RF Exposure
Limits and guidelines for RF exposure come from:

• US FCC limits for the general population. See the FCC web site at http://www.fcc.gov,
and the policies, guidelines, and requirements in Part 1 of Title 47 of the Code of Federal
Regulations, as well as the guidelines and suggestions for evaluating compliance in FCC
OET Bulletin 65.
• Health Canada limits for the general population. See the Health Canada web site at
http://www.hc-sc.gc.ca/ewh-semt/pubs/radiation/99ehd-dhm237/limits-limites_e.html and
Safety Code 6.
• EN 50383:2002 Basic standard for the calculation and measurement of electromagnetic
field strength and SAR related to human exposure from radio base stations and fixed
terminal stations for wireless telecommunication systems (110 MHz - 40 GHz).
• ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for
the general public. See the ICNIRP web site at http://www.icnirp.de/ and Guidelines for
Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields.
7
1.8.3 Power Density Exposure Limit
The applicable power density exposure limit from the documents referenced above is 10
2
W/m for RF energy in the 2.4 GHz, 5.2 GHz, 5.4 GHz, 5.8 GHz and 5.9 GHz frequency
bands.
Peak power density in the far field of a radio frequency point source is calculated as follows:
Equation 1 - Peak power density in the far field

P .G
S=
4π d 2
Where: Is:
S Power density in W/m2.
P Maximum Average transmit power capability of the radio, in Watts
G Tx gain factor converted from dBi
d Distance from point source, in metres
Rearranging terms to solve for distance yields:

P.G
d=
4π .S
1.8.4 Calculated Distances and Power Compliance Margins
Table 3 shows calculated minimum separation distances d, recommended distances and

resulting power compliance margins for each frequency band and antenna combination.
These are conservative distances that include compliance margins. At these and greater
separation distances, the power density from the RF field is below generally accepted limits
for the general population.
8
Table 3 - Power Compliance Margins

Band Antenna Max Equation Variables Recommended Power
Average
P G S d Distance (m) Compliance
Transmit
Power in (Watt) (factor) (W/m2) (m)
Margin
Burst
(Watt)
2.5
GHz Integrated 0.25 0.125 63 10 0.25 2 8.0
4.5
GHz Integrated 0.5 0.4 158 10 0.71 5 7.0
4.8 Integrated 0.5 0.4 158 10 0.71 5 7.0

GHz
Connectorized 0.5 0.4 398 10 1.1 5 4.5
4.9 Integrated 0.25 0.2 158 10 0.5 2 4.0

GHz
Connectorized 0.25 0.2 398 10 0.8 5 6.25
Integrated 0.005 0.00250 200 10 0.06

1 15.9
5.4 External 4ft
GHz Dish 0.00035 0.00017 2884 10 0.06
Integrated 0.32 0.16 200 10 0.5 2 4.0
5.8 External 2ft

GHz Flat Plate 0.32 0.16 631 10 0.9 4 4.5
External 6ft
Dish 0.32 0.16 6310 10 2.83 10 3.5
Integrated 0.32 0.16 200 10 0.5 2 4.0
5.9 External 2ft

GHz Flat Plate 0.32 0.16 631 10 0.9 4 4.5
External 6ft
Dish 0.32 0.16 6310 10 2.83 10 3.5
NOTE
Gain of antenna in dBi = 10*log(G).
The regulations require that the power used for the calculations is the maximum
power in the transmit burst subject to allowance for source-based time-averaging.
At 5.4 GHz and EU 5.8 GHz, the products are generally limited to a fixed EIRP which
can be achieved with the Integrated Antenna. The calculations above assume that
the maximum EIRP allowed by the regulations is being transmitted.
9
NOTE
If there are no EIRP limits in the country of deployment, use the distance calculations
for FCC 5.8 GHz for all frequency bands.
At FCC 5.8 GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance
proportionally to the antenna gain.
At 2.5 GHz, for antennas between 1.2m (4ft) and 3.6m (12ft) the safe distance is
increased to between 0.8m (2.6 ft) and 2.4m (7.8 ft).
1.9 Compliance with Regulations
1.9.1 General
Changes or modifications not expressly approved by Motorola could void the user’s authority
to operate the system.
This system has achieved Type Approval in various countries around the world. This means
that the system has been tested against various local technical regulations and found to
comply. The frequency bands in which the system operates may be ‘unlicensed’ and, in these
bands, the system can be used provided it does not cause interference. Further, it is not
guaranteed protection against interference from other products and installations.
CAUTION
When planning a link that will use Connectorized PTP 600 Series bridges (with
external antennas), ensure that regulatory requirements are met for the installation,
as described in Section 10.5 Regulatory Issues with Connectorized Units.
1.9.2 FCC and ETSI Compliance Testing
The system has been tested for compliance to both US (FCC) and European (ETSI)
specifications. It has been shown to comply with the limits for emitted spurious radiation for a
Class B digital device, pursuant to Part 15 of the FCC Rules in the USA and appropriate
European ENs. These limits have been designed to provide reasonable protection against
harmful interference. However the equipment can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to
other radio communications. There is no guarantee that interference will not occur in a
particular installation.
NOTE
A Class B Digital Device is a device that is marketed for use in a residential
environment, notwithstanding use in commercial, business and industrial
environments.
10
1.9.3 Radio and Television Interference
If this equipment does cause harmful interference to radio or television reception, which can
be determined by turning the equipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:
• Reorient or relocate the Outdoor Unit (ODU).
• Increase the separation between the affected equipment and ODU.
• Connect the ODU and PIDU Plus into a power outlet on a circuit different from that to
which the receiver is connected.
• Consult your installer or supplier for help.
1.9.4 Deployment and Operation
The Radio Regulations of various countries’ limits constrain the operation of radio products
generally. In particular the local regulator may limit the amount of conducted or radiated
transmitter power and may require registration of the radio link.
The power transmitted by the PTP 600 Series Bridge is controlled by the use of Region-
specific License Keys. Contact your supplier/installer to ensure that your product is set for the
correct License Key for your Country/Region and to ensure that you have fulfilled all the local
regulatory requirements, especially if you are intending to use a link with external antennas.
1.9.5 Examples of Regulatory Limits
For examples of how the regulatory limits apply to each frequency variant in specific
countries, refer to:
• Section 17.2.1 PTP 25600 Examples of Regulatory Limits
11
1.9.6 Registration of Links
UK Registration of Links – OfCom, The application form may be found at:
http://www.ofcom.org.uk/radiocomms/isu
Eire Registration of Links – Commission for Communication Regulation, The application form
may be found at:
http://www.comreg.ie/licensing_and_services
12
2 Product Description
This section provides a high level description of the PTP 600 product. It describes in general
terms the function of the product, the main product variants and typical deployment. It also
describes the main hardware components.
The following topics are described in this section:

• 2.1 Product Function
• 2.2 Typical Deployment
• 2.3 Frequency Variants
• 2.4 Other Product Variants
• 2.5 Network Connection
• 2.6 Outdoor Unit (ODU)
• 2.7 PIDU Plus PTP 300/500/600 Series
• 2.8 Redundancy and Alternative Powering Configurations
• 2.9 Remote LEDs and Recovery Switch
• 2.10 Cables and Connectors
• 2.11 PTP and Lightning Protection
• 2.12 Mounting Brackets
2.1 Product Function

The PTP 600 Series Bridge has been developed to provide Point-to-Point data connectivity
via a wireless Ethernet bridge operating at broadband data rates.
The PTP 600 Series Bridge offers true non-line-of-sight (NLOS) operation by using a
combination of Orthogonal Frequency Division Multiplexing (OFDM) modulation and Multiple-
Input Multiple-Output (MIMO) techniques. These technologies enable the PTP 600 Series
Bridge to drive through foliage and around buildings to such an extent that almost universal
coverage can be expected at short range.
The PTP 600 Series Bridge has been designed to coexist with other users of the band in an
optimal fashion using a combination of Transmit Power Control (TPC), Spectrum
Management functionality and Antenna beam shape. In order to maintain link availability, the
product employs adaptive modulation techniques that dynamically reduce the data rate in
severe or adverse conditions.
13
2.2 Typical Deployment

The PTP 600 Series Bridge consists of an identical pair of units deployed one at each end of
the link. The radio link operates on a single frequency channel in each direction using Time
Division Duplex (TDD). One unit is deployed as a master and the other as a slave. The
master unit takes responsibility for controlling the link in both directions.
The PTP 600 Series Bridge is aimed at a wide range of applications. An example application
is an enterprise that has a requirement to connect together the Local Area Network (LAN) of
two or more buildings as shown in Figure 1.
Figure 1 - Typical PTP 600 Series Bridge Deployment
Each end of the link consists of:

• Outdoor Unit (ODU): An integrated (or connectorized – see Section 10 Connectorized
PTP 600 Series Bridge) outdoor transceiver unit containing all the radio and networking
electronics.
• PIDU Plus: An indoor connection box containing a mains power supply, status indicators
and network connection port.
A pair of units is normally supplied pre-configured as a link.
14
2.3 Frequency Variants

The PTP 600 Series Bridge has been developed to operate within license exempt frequency
bands as well as the licensed 2.5 GHz band in the USA. The frequency variants are listed in
Table 4.
Table 4 - PTP 600 Series Bridge Frequency Variants

Variant Region Frequency Variable Channel
Coverage Channel Raster
Bandwidth
PTP FCC BRS-EBS Post- 2496-2568 MHz 5, 10, 15, 30 5.5 MHz
25600 Transition Band MHz
2572-2614 MHz 5, 10, 15, 30 6 MHz
MHz
2618-2690 MHz 5, 10, 15, 30 5.5 MHz
MHz
PTP US Federal 4404-4596 MHz 5, 10, 15, 20 6 MHz
45600 MHz
4404-4596 MHz 30 MHz 10 MHz
NTIA 4400-4600 MHz 10, 20 MHz 6 MHz
PTP US Federal 4710-4940 MHz 5, 10, 15, 20, 5 MHz

48600 MHz
US Federal Extended 4710-5000 MHz 5, 10, 15, 20, 5 MHz
MHz
NTIA 4700-4940 MHz 10, 20 MHz 5 MHz
PTP USA/Canada Public 4940-4990 MHz 5, 10, 20 MHz 5 MHz

49600 Safety
Hong Kong Public 4900-4950 MHz 5, 10, 20 MHz 5 MHz
Safety
PTP ETSI 5 GHz Band B 5470-5725 MHz 5, 10, 15 MHz 6 MHz
54600
FCC UNII Band
5470-5725 MHz 30 MHz 10 MHz
PTP ETSI 5 GHz Band C 5725-5850 MHz 5, 10, 15 MHz 6 MHz

58600
FCC ISM Band
5725-5850 MHz 30 MHz 10 MHz
PTP Russia 5825-5925 MHz 5, 10, 15 MHz 6 MHz

59600
30 MHz 10 MHz
15
Variant Region Frequency Variable Channel

Coverage Channel Raster
Bandwidth
PTP India 5875-5925 MHz 5, 10, 15 MHz 6 MHz
59600
30 MHz 10 MHz
NOTE
For PTP 25600, channel widths of 30 MHz are available where allowed by local
regulations and subject to some restrictions on channel choice.
For PTP 58600 ETSI 5 GHz Band C, use of the product is only allowed where
permitted by country-specific regulations.
2.4 Other Product Variants

The Lite versions have lower data throughput rates then the Full versions.
The PTP 600 outdoor unit (ODU) may be integrated (with its own antenna) or connectorized
(with a separate antenna).
2.5 Network Connection

The network connection to a PTP 600 Series Bridge is made via a 1000BaseT Ethernet
connection. Power is provided to the ODU over the 1000BaseT Ethernet connection using a
patented non-standard powering technique.
Previous releases of the PTP 600 Series Bridge platform used different powering and
connection arrangements. Users of equipment prior to “Mod Record 1” should refer to the
User Guide shipped with the original equipment. The “Mod Record” label can be found on the
back of the ODU as shown in Figure 2.
Figure 2 - Mod Record Label
16
Alternatively, the network connection to a PTP 600 Series Bridge can be made using a
1000BaseSX Fiber Optic cable connected directly to the ODU. In this case power is still
provided over the 1000BaseT Ethernet connection. In the case of Fiber Optic cable failure the
PTP 600 Series Bridge will automatically fall back to the copper Ethernet connection
(provided the cable length <=100m [330 ft]). “PTP 600 Series Optical Interface Upgrade Kits”
can be obtained from your distributor, reseller or system integrator.
2.6 Outdoor Unit (ODU)

The ODU is a self-contained unit. It houses both radio and networking electronics. The ODU
for the PTP 600 Series Bridge should only be deployed using the supplied PIDU Plus PTP
300/500/600 Series. Figure 3 shows an installation example of a PTP 600 Series ODU with a
Motorola lightning protection unit (PTP-LPU).
Figure 3 – PTP 600 Series Bridge Outdoor Unit (ODU) with PTP-LPU
17
2.7 PIDU Plus PTP 300/500/600 Series

The PIDU Plus PTP 300/500/600 Series (Figure 4) is used to generate the ODU supply
voltage from the mains supply (or from an external DC source) and inject this supply voltage
into the 1000BaseT Ethernet connection to the ODU. Connection uses a CAT5e cable using
standard RJ45 wiring.
CAUTION
Care should be taken not to connect equipment other than an ODU or LPU for the
PTP 600 Series Bridge to a PIDU Plus ODU port, as equipment damage may occur.
The PIDU Plus PTP 300/500/600 Series is not interchangeable with the PIDU Plus
PTP 400 Series.
Figure 4 - Power Indoor Unit (PIDU Plus PTP 300/500/600 Series)
2.7.1 Power and Ethernet LEDs
The front panel contains indicators showing the status of the power and Ethernet
connections:
• The Power indicator is illuminated when the PIDU Plus is receiving mains power.
• The Ethernet indicator normally illuminates when the Ethernet link is working, flashing
when there is Ethernet activity. The fact that it lights also indicates that the ODU is
powered. At power up the LED will flash 10 times to indicate that a correct start up
sequence has occurred. See Section 9 Fault Finding for further fault finding information.
18
2.7.2 ODU, LAN and Recovery
At the bottom of the PIDU Plus is an entry point for the PIDU Plus to ODU cable, the
1000BaseT Ethernet network port and the Recovery switch.
Figure 5 – PIDU Plus Recovery Switch Location
The Recovery switch is used to recover the unit from configuration errors or software image
corruption. To put an ODU into recovery mode, the Recovery switch should be pressed, then
the power applied. The Recovery switch should be kept pressed for at least 20 seconds after
the power has been applied. Full instruction on the recovery mode can be found in Section 8
Recovery Mode.
A simple reboot can be performed by removing and re-applying the mains power to the PIDU
Plus.
2.7.3 DC In and Out
On the left hand side of the PIDU Plus, 48V DC input and output connections can be found.
These are used to power the PTP 600 Series Bridge from an external DC source or to
provide a level of power supply redundancy, as shown in Section 2.8 Redundancy and
Alternative Powering Configurations.
2.7.4 Remote Connectors and Jumpers
Also on the left hand side of the PIDU Plus, connectors and jumpers can be found that allow
the remote connection of power LED, Ethernet LED and Recovery switch. The connection
instructions can be found in Section 2.9 Remote LEDs and Recovery Switch.
19
2.7.5 Mains Connection
The input supply range for the PIDU Plus is 90V-264V AC, 47-63Hz. Mains connection to the
PIDU Plus is made using a standard “figure of eight” mains lead as shown in Figure 6.
Figure 6 – PIDU Plus Power Input
20
2.8 Redundancy and Alternative Powering Configurations

The PTP 600 Series Bridge can be powered from an external DC source and can be provided
with power supply redundancy as follows:
• External DC supply only (Figure 8): This configuration is for use where there is no mains
supply.
• External DC supply and AC supply (Figure 9): This configuration provides redundancy
through the use of mains and DC supply.
• External DC supply and redundant AC Supply (Figure 10): This configuration guards
against mains failure and failure of the DC output of single PTP 300/500/600 PIDU Plus.
NOTE
The use of DC supplies of less than 55v will reduce the usable distance between the
PIDU Plus and ODU (Figure 7).
Figure 7 – Relationship Between DC Voltage and Cable Length
CAUTION
The maximum distance from the ODU to the connected network equipment is 100m
(330 ft) when using 1000BaseT. Powering distances over 100m (330 ft) are only
applicable when using a 1000BaseSX (Fiber Optic) connection.
21
Figure 8 - External DC Supply Only
Figure 9 - External DC Supply and AC Supply
Figure 10 - External DC Supply and Redundant AC Supply
22
2.9 Remote LEDs and Recovery Switch

The PIDU Plus provides a facility to connect remote LEDs and Recovery switch allowing the
PIDU Plus to be mounted inside an enclosure. At the left hand end of the PIDU Plus under
the ODU connection cover can be found a PCB header and three jumpers. Jumpers J906 and
J907 should be removed and connection to the remote LEDs and Recovery switch made to
J908 as shown in Figure 11.
Figure 11 - Remote LED and Recovery Switch Wiring
2.10 Cables and Connectors

The cable used to connect the PIDU Plus to the ODU can be any standard CAT5e type
provided that it is UV resistant and suitable for outdoor deployment. Motorola recommends
that cables to the specification below be used:
Cable: Superior Essex BBDGE CAT 5e
Connector Type: Tyco, 5-569278
Gland: Motorola WB1811
CAUTION
Failure to use the recommended (or equivalent) standard of cable may invalidate the
system’s safety certification.
23
The cable used to connect the PIDU Plus to the users Network Equipment can be any
standard CAT5e Cable.
The PIDU Plus to ODU and the PIDU Plus to Network Equipment cables may be unscreened
(UTP) or screened (STP). However, unscreened cables reduce the system’s ability to cope
with nearby lightning strikes. If lightning activity is common in the area of deployment, the use
of screened cable is highly recommended. See Section 5 Lightning Protection.
The PIDU Plus provides screen continuity between the ODU and Network Equipment
connections.
NOTE
The ODU network connection implements automatic MDI/MDI-X sensing and pair
swapping allowing connection to networking equipment that require cross-over cables
(MDI-X networks) or straight-through cables (MDI Networks).
2.11 PTP and Lightning Protection

The PIDU Plus meets the low level static discharge specifications identified in Section 17 PTP
600 Reference Information, but does not provide lightning or surge suppression.
The amount of lightning protection is dependent on regulatory requirements and the end user
requirements. The standard ODU for the PTP 600 Series Bridge is fitted with surge limiting
circuits and other features to minimize the risk of damage due to nearby lightning strikes. To
be fully effective, these standard features require some additional equipment to be configured
as part of the system installation.
A separate Ethernet surge suppressor must be used and appropriately earthed. Suitable
surge suppressors can be sourced from your Motorola Point-to-Point Distributor or Solutions
Provider. See Section 5 Lightning Protection.
CAUTION
Motorola recommends the use of screened cable and Lightning Protection units to
protect connected equipment from nearby strikes.
The PTP 600 Series Bridge is not designed to survive direct lightning strikes. For this
reason the unit should not be installed as the highest point in a localized area, unless
specific precautions are taken. See Section 5 Lightning Protection.
24
2.12 Mounting Brackets

The ODU is supplied with a bracket for mounting it to a pole of 50mm (2”) to 75mm (3”) in
diameter. For more details on mounting, see Section 6 Installation.
The bracket allows for adjustment in both azimuth and elevation. The bracket may be split to
allow the pole mount section of the bracket to be mounted to the pole first. This allows the
installer to take the weight of the unit and secure it, one handed, with a single mounting bolt.
• The PIDU Plus can either be desk or wall mounted. The preference is wall mounted, with
the cables dressed to a cable channel. Wall mounting is achieved by screwing through
the mounting lugs on either side of the unit. Remember to leave space for access to the
Recovery button. See Section 2.7 PIDU Plus PTP 300/500/600 Series.
25
3 Product Features
3 Product Features
This section provides descriptions of the main features of PTP 600 product architecture.

• 3.1 Ethernet Frames
• 3.2 Management Function
• 3.3 Configuration and Management
• 3.4 Channel Bandwidth and Link Symmetry Control
• 3.5 Non Line Of Sight (NLOS) and Line Of Sight (LOS)
• 3.6 Upgradeable Software
• 3.7 Networking Information
• 3.8 Time Division Duplex (TDD) Synchronization
• 3.9 Link Mode Optimization
• 3.10 Telecoms Circuits
• 3.11 Radar Avoidance
3.1 Ethernet Frames

The PTP 600 series provides wireless Ethernet bridging between two fixed locations. To be
more precise, it forwards Ethernet frames as a two-port transparent heterogeneous
encapsulation bridge, meaning that each bridge forwards frames between two dissimilar
interfaces (Ethernet and wireless), encapsulating Ethernet MAC frames within a PTP MAC
frames for transmission at the wireless interface. A link consisting of a pair of back to back
bridges appears to the data network to be very similar to a standard two-port Ethernet bridge.
The PTP 600 series provides eight traffic classes, classifying Ethernet frames into one of
eight prioritized queues based on inspection of the user priority field (802.1p) in a customer
(IEEE802.1Q) VLAN tag or provider (IEEE802.1ad) VLAN tag. Untagged frames receive a
default priority. The scheduling method is strict priority. The bridge does not implement any
VLAN functions for bridged frames apart from inspection of the priority field, and consequently
the bridge forwards tagged and untagged Ethernet frames regardless of VLAN ID and without
modification of any protocol header field.
The PTP 600 series supports a maximum Ethernet frame size of 2000 bytes for bridged
traffic.
26
3 Product Features
3.2 Management Function

The management function of the PTP 600 Series Bridge is logically equivalent to a separate
protocol stack with virtual point of attachment at the Ethernet interface. This is illustrated in
Figure 12.
Figure 12 – PTP 600 Series Bridge Layer Diagram
Each unit in the link is manageable through an IP connection. Standard IP protocols are
utilized for all management functions, for example, HP, SNMP, etc. The unit can be
configured to use a VLAN with a single C-tag or S-tag on the management interfaces.
3.3 Configuration and Management

Configuration and Management of the PTP 600 Series Bridge is implemented using an inbuilt
web server hosting a number of Configuration and Management web pages. This approach
allows Configuration and Management to be carried out on any standard web browsing
technology. The PTP 600 Series Bridge can also be managed remotely using the SNMP
management protocol. Connection to the bridge is via the Ethernet connection carrying the
bridge network traffic. Connection to the unit is via a preset IP address. This address can be
changed via the Network Interface Configuration web page. A full explanation of the available
web pages and their use can be found in Section 7 Web Page Reference.
27
3 Product Features
3.4 Channel Bandwidth and Link Symmetry Control

The PTP 600 series provides configurable channel bandwidth in the radio link (5 MHz, 10
MHz, 15 MHz, 20 MHz and 30 MHz depending on the frequency band for the bandwidth
choice), and configurable fixed and adaptive link symmetry. Fixed link symmetry supports:
• 2:1
• 1:1
• 1:2
Channel bandwidth 5 MHz supports link symmetry 1:1 only. Adaptive link symmetry is not
available in radar regions.
3.5 Non Line Of Sight (NLOS) and Line Of Sight (LOS)

The PTP 600 Series Bridge is designed to operate in both Non Line Of Sight (NLOS) and
Line Of Sight (LOS) environments.
3.6 Upgradeable Software

The PTP 600 Series Bridge is fully software upgradeable. New software images are first
downloaded from the Motorola website http://www.motorola.com/ptp to a convenient
computer. The image is then uploaded to the ODU via the web management page described
in Section 7.8 Software Upgrade. The compressed image is first loaded into RAM and check-
summed. If the compressed image transfer has completed successfully the image is
decompressed and written to flash memory. On completion of this process the unit can be
rebooted to use the newly uploaded image. Should this process fail, the unit will revert to a
protected compressed image installed during manufacturing to allow the unit to be recovered.
3.7 Networking Information

The PTP 600 Series Bridge operates as a transparent Ethernet bridge. Although each unit
requires an IP address, this IP address is for management purposes only, and it plays no part
in the forwarding of bridged Ethernet frames. IP addresses are assigned during initial
configuration as described in Section 6 Installation.
28
3 Product Features
3.8 Time Division Duplex (TDD) Synchronization
3.8.1 Introduction
In a TDD system, a radio transmits for a portion of the radio frame and receives in a different
portion of the frame. Motorola PTP600 links consist of a Master unit and a Slave unit with the
Master transmitting for the first part of the radio frame (Slave receiving) and the Slave
transmitting in the remainder of the radio frame (Master receiving). The portion of the frame
apportioned to each period can be dynamic, for example in IP optimization mode where the
split is a function of the offered traffic in each direction. However, if the frames of the two links
are not aligned in time, then an interference mechanism exists where one Master unit may be
transmitting when the Master unit from the other link is receiving. A similar mechanism exists
for Slave units. The level of interference becomes very significant when the units are located
in close proximity, for example when units are located on the same mast. This problem is
illustrated in Figure 13 where it can be seen that transmissions from Master unit A overlap
with the receive portion of Master unit B and vice versa.
Figure 13 - Co-location of Links Interference Problem - A Simple Example
29
3 Product Features
Interference can be minimized by increasing the radio channel separation between units
which are in close proximity, for example for units on the same mast. This may not always be
possible if the mast is hosting a large number of links and if spectrum is limited. Also, the
achieved reduction may not always be sufficient. Another way to reduce interference is to
reduce the transmit power of an interfering radio. Again, this may not always be possible if the
link causing the interference does not itself have sufficient radio gain margin to allow the
power of its radios to be reduced.
3.8.2 TDD Synchronization
TDD synchronization overcomes these issues by aligning the radio frame of all links in the
network such that all Master units transmit at the same time and receive at the same time.
This eliminates interference between units on the same mast if the units on the mast are
configured as Master units. This illustrated in Figure 14 where the frames of the two links are
aligned in time.
Figure 14 - TDD Synchronization And Co location Example
Due to propagation delay, a mechanism exists where an interfering signal from a remote
Master unit arrives at a victim Master delayed in time. This would occur when Master units
are installed on different masts. Similarly, an interfering signal from a remote Slave unit will
arrive at a victim Slave unit delayed in time. Correct configuration of TDD synchronization
ensures that the delayed signals do not overlap with the receive portion of the victim frame. In
order to eliminate the interference from delayed signals, the configuration and the resulting
TDD frame structure will actually depend upon characteristics of the overall network such as
the longest link and the maximum distance between interfering Master units and interfering
Slave units. The installation process requests that these parameters are entered when TDD
synchronization is enabled. This is covered in detail in Section 11 TDD Synchronization
Installation and Configuration.
30
3 Product Features
3.8.3 Implementation of TDD Synchronization
TDD synchronization is achieved by connecting each Master unit to a GPS Synchronization

Unit. Installation details are covered in Section 11 TDD Synchronization Installation and
Configuration. The GPS unit provides the Master unit with a precise 1Hz signal where the
leading edge occurs at the same point in time for all units in the network which have been
locked to the GPS Satellite system. The Master radio then aligns its radio frame to start on
the leading edge of the 1Hz signal.
3.8.4 System Constraints with TDD Synchronization Enabled
The following constraints apply when TDD synchronization is enabled:

• As the radio frame needs to be aligned across the network, the apportioning of the frame
between the two link directions can no longer be dynamic. The split is fixed at 1:1.
• In order that the start of the radio frame can always align with the leading edge of the 1Hz
signal, the radio frame duration must be an integer fraction of 1s.
31
3 Product Features
3.9 Link Mode Optimization

Link Mode Optimization allows the PTP 600 link to be optimized according to the type of
traffic that will be bridged. The link supports two modes: IP mode and TDM mode.
3.9.1 IP Link Mode Optimization
IP mode is optimized to provide the maximum possible link capacity. IP mode is an

appropriate choice where applications in the bridged networks provide some measure of
reliable transmission, and where very low latency is not critical.
IP mode supports both fixed and adaptive link symmetry (see Section 3.4 Channel Bandwidth
and Link Symmetry Control).
3.9.2 TDM Link Mode Optimization
TDM mode is optimized to provide the lowest possible latency. TDM mode additionally
implements a more conservative approach to adaptive modulation, leading to lower error
rates in fading channels at the expense of slightly lower link capacity. TDM mode is an
appropriate choice for delay intolerant data without reliable transmission (for example voice
over IP data).
TDM mode supports fixed link symmetry only (see Section 3.4 Channel Bandwidth and Link
Symmetry Control).
TDM mode is selected automatically when Telecom interfaces are enabled.
32
3 Product Features
3.10 Telecoms Circuits

The PTP 600 link provides native support for one or two E1 links, or one or two T1 links. The
link relays unstructured E1 or T1 data and provides accurate timing transfer.
3.10.1 Lowest Telecoms Modulation Mode
In narrow channel bandwidth and lower modulation modes, the link may have insufficient
capacity to relay the E1/T1 payload; in this case, the wireless link continues to carries timing
information in order to maintain accurate clock synchronization. The relay of telecoms data
resumes automatically when the link reaches a suitable modulation mode.
Links that are able to operate consistently in a high modulation mode can take advantage of
lower link latency. This option is configured by setting the "Lowest Telecoms Modulation
Mode" during installation. Appropriate settings for this control may be determined by using the
LINKPlanner tool. The reduction in latency is achieved by disabling the relay of telecoms data
in lower modulation modes, and this necessarily results in somewhat lower availability for the
telecoms circuit. The loss of availability can be estimated using the LINKPlanner.
The unit will override the user setting of Lowest Telecoms Modulation Mode if the selected
mode has insufficient capacity to carry the telecoms data, or if the mode demands very high
latency and requires more buffering than the link can provide. When the effective mode differs
for Single and Dual Payload operation two modes will be displayed: "Lowest Dual Payload
Modulation Mode" and "Lowest Single Payload Modulation Mode".
3.10.2 Fixed Frequency Operation
In the PTP 600 link, data errors may occur during channel changes on an operational link. It
may be appropriate to minimize channel-change-related errors in a link carrying Telecoms
traffic by preventing channel changes initiated by i-DFS. This can be achieved by barring all
channels except one in the Spectrum Management page, or alternately by selecting Fixed
Frequency mode. These steps unavoidably disable interference avoidance mechanisms, and
should not be taken if the risk of errors due to interference is more severe than the risk due to
channel changes.
33
3 Product Features
3.10.3 Further Reading
Installation details are provided in Section 12 E1/T1 Installation Guide.
E1/T1 circuits are configured using the web pages described in Section 7.5.5 Telecoms
Configuration and 7.7.4.1 Telecoms Interface.
3.11 Radar Avoidance

Radar Avoidance requires that equipment used in the region:
• Detects interference from other systems and avoids co-channel operation with these
systems, notably radar systems.
• Provide on aggregate a uniform loading of the spectrum across all devices, that is, Fixed
Frequency operation is not allowed.
To address the primary aims, the Spectrum Management algorithm implements a radar
detection function which looks for impulsive interference on the operating channel only. If
impulsive interference is detected, Spectrum Management will mark the current operating
channel as having detected radar (unavailable channel) and initiate a channel hop to an
available channel. The previous operating channel will remain in the unavailable state for
thirty minutes after the last impulsive interference pulse was detected. After the thirty minutes
have expired the channel will be returned to the usable channel pool.
The equipment can only transmit on available channels, of which there are none at initial
power up. The radar detection algorithm will always scan a usable channel for 60 seconds
for radar interference before making the channel an available channel. This compulsory
channel scan will mean that there is a 60 seconds service outage every time radar is detected
and that the installation time is extended by 60 seconds even if there is found to be no radar
on the channel.
NOTE
On system installation or start-up this extends the initial scan time of the Master unit
by 60 seconds. To address the requirement to provide aggregate uniform loading of
the spectrum across all devices, the channel selection algorithm will choose a
channel at random from a list of useable channels. The channel selection algorithm is
initiated at link initialization and when radar interference is detected.
34
4 Planning Considerations
This section provides information to help the user to plan a PTP 600 link.
Each frequency variant has specific licensing restrictions that affect frequency range, channel
bandwidth, maximum power and radar avoidance. Link planning must take account of
obstructions, site selection, path loss and wind loading.

• 4.1 Spectrum Planning
• 4.2 Licenses and Region Codes
• 4.3 Radar Avoidance and Bandwidth Operation
• 4.4 Variable Channel Bandwidth Operation
• 4.5 Link Planning
• 4.6 Site Selection Criteria
• 4.7 Wind Loading
• 4.8 Path Loss Considerations
• 4.9 System Threshold, Output Power and Link Loss
To calculate the data throughput capacity of a planned PTP 600 link, see Section 13 Data
Rate Calculations.
4.1 Spectrum Planning

The PTP 600 may use one of four alternative methods of spectrum planning. The choice of
methods depends upon whether or not the region mandates radar detection.
4.1.1 Regions Without Mandatory Radar Detection
In regions that do not mandate DFS (Radar Detection), the frequencies may be configured
symmetrically or asymmetrically (different transmit and receive frequencies). The Spectrum
Management Control options are:
• Intelligent Dynamic Frequency Selection (i-DFS): This method continually monitors the
spectrum looking for the channel with the lowest level of on channel and co-channel
interference. Statistical techniques are used to select the most appropriate transmit and
receive channels. The i-DFS mode can be influenced in its channel decision process by
selectively barring channels from use.
35
• Fixed Frequency: This method allows the installer to allocate fixed transmit and receive
frequencies on the units.
4.1.2 Regions With Mandatory Radar Detection
In regions that mandate DFS (Radar Detection), the frequency must always be symmetrical
(transmit and receive on the same frequency). The Spectrum Management Control options
are:
• Dynamic Frequency Selection (DFS): This method detects interference from other
systems and avoids co-channel operation with these systems, notably radar systems.
• DFS with i-DFS: This method is similar to i-DFS. It differs in the event that several
alternative channels are equally the best within the 1 dB measurement resolution. In i-
DFS, the ODU selects the lowest channel number out of the set of best channels. In DFS
with i-DFS, the ODU makes a random selection from the equal best channels.
4.2 Licenses and Region Codes

The PTP 600 Series Bridge uses a system of Region Codes to control the operation of the
radio link. The user must ensure the product is configured to conform to local regulatory
requirements by installing a License Key for the correct Region Code.
CAUTION
For the connectorized model, when using external antennas of higher gain than the
appropriate integrated antenna, the regulations may require the maximum Tx power
to be reduced. To ensure that regulatory requirements are met for connectorized
installations, refer to Section 10.5 Regulatory Issues with Connectorized Units.
The license and region codes for each frequency variant are listed in:
• Section 17.2.2 PTP 25600 Licenses and Region Codes
36
4.3 Radar Avoidance and Bandwidth Operation

Where regulatory restrictions apply to certain channels these channels are barred. RTTT
avoidance may be necessary in all channel bandwidths. The number of channels barred is
dependant on the channel raster selected. For example see the effect of the UK RTTT
channel restrictions in the 30 MHz bandwidth (Figure 15), where blocks in red indicate
channels that are barred. Barred channels are indicated by a “No Entry” symbol displayed on
the “Spectrum Management” web page, see Section 7.9.11 Spectrum Management Control
with Radar Avoidance.
Figure 15 - 5.8 GHz UK RTTT Channel Avoidance – 30 MHz Channel Bandwidth (Example)
NOTE
Radar avoidance requirements in the 5.4GHz band in the EU is detailed in
specification EN 301-893 version V1.4.1 plus additional requirements shown in the
OJ of the EC and in the US in the specification FCC part 15.407. Radar avoidance at
5.8 GHz is applicable to EU operation and the requirements are currently as defined
in EN 302 502.
37
4.4 Variable Channel Bandwidth Operation

The selection of Channel Bandwidth depends upon the PTP frequency variant:
• For PTP 25600, PTP 45600, PTP 54600, PTP 58600 and PTP 59600, Channel
Bandwidth may be 30, 15, 10 or 5 MHz.
• For PTP 48600 and PTP 49600, Channel Bandwidth may be 20, 10 or 5 MHz.
The 30MHz channel widths are available where allowed by local regulations and subject to
some restrictions on channel choice.
Lite versions of the PTP 600 products do not support a Channel Bandwidths of 5 MHz.
Configuration of the variable bandwidth operation must be symmetric, that is, the Transmit
and receive channels must use identical Channel Bandwidths.
For details of the spectrum settings that are available to each frequency variant, refer to:
• Section 17.2.6 PTP 25600 Available Spectrum Settings
38
4.5 Link Planning
4.5.1 Range and Obstacles
The PTP 600 Series are designed to operate in Non-Line-of-Sight (NLoS) and Line-of-Sight
(LoS) environments.
The PTP 600 Series Bridge will operate at ranges from 100 m (330 ft) to 200 km (124 miles),
within 3 modes: 0-40km (0-25 miles), 0-100km (0-62 miles) and 0-200km (0-124 miles).
Operation of the system will depend on obstacles in the path between the units. Operation at
40 km (25 miles) or above will require a near line-of-sight path. Operation at 100m (330 ft)
could be achieved with one unit totally obscured from the other unit, but with the penalty of
transmitting at higher power in a non-optimal direction, thereby increasing interference in the
band.
A survey must be performed to identify all the obstructions (such as trees or buildings) in the
path and to assess the risk of interference. This information is important if you are to achieve
an accurate link feasibility assessment.
4.5.2 PTP LINKPlanner
Link planning enables a link of known quality to be installed. This involves the acquisition of
path profile data (using Motorola’s free LINKPlanner utility). The LINKPlanner predicts data
rates and reliability over the path. It allows the user to try different antenna heights and RF
power settings. When the link is installed, the mean path loss can be checked to confirm that
the predicted data rate and link reliability is achievable. Motorola LINKPlanner is available to
download from http://www.motorola.com/ptp/support.
39
4.6 Site Selection Criteria

The following are guidelines for selecting the installation location of the ODU and PIDU Plus
for a PTP 600 Series Bridge.
4.6.1 ODU Site Selection
When selecting a site for the ODU the following should be taken into consideration:
• It should not be possible for people to stand or walk in front of the antenna
• Height and location to achieve the best radio path
• Height in relation to other objects with regard to lightning strikes
• Aesthetics and planning permission issues
• Distance from the ODU and connected Network equipment (Maximum cable run from the
ODU to the connected equipment is 100m [330 ft])
• Distance from the PIDU Plus to the ODU (Maximum cable run from the PIDU Plus to the
ODU is 300m [990 ft] when using the Fiber interface)
• If using the GPS Sync Unit, ensure that it is exposed to an unobstructed path to the sky.
Please refer to the “GPS Synchronization Unit Kit” User Manual delivered with the kit.
• The effect of strong winds on the installation – see Section 4.7 Wind Loading.
4.6.2 PIDU Plus Site Selection
When selecting a site for the PIDU Plus the following should be taken into consideration:
• Availability of a mains electricity supply
• Accessibility for viewing status indicators and pressing Recovery switch.
4.7 Wind Loading

Antennas and electronic equipment mounted on towers or pole mounted on buildings will
subject the mounting structure to significant lateral forces when there is appreciable wind.
Antennas are normally specified by the amount of force (in pounds) for specific wind
strengths.
The magnitude of the force depends on both the wind strength and size of the antenna.
40
4.7.1 Calculation of Lateral Force
The PTP 600 Series bridge with or without the integral antenna is essentially a flat structure
and so the magnitude of the lateral force can be estimated from:
2
Force (in pounds) = 0.0042 . A . v
Where A is the surface area in square feet and v is the wind speed in miles per hour.
The lateral force produced by a single 600 Series bridge (integrated or connectorized model)
at different wind speeds is shown in Table 5 and Table 6.
Table 5 - Lateral Force – Imperial

Largest Surface Lateral Force (Pound) at wind speed (mph)
Area (sq ft)
80 100 120 140 150
PTP 600 Series 1.36 36.6 57.1 82.3 146.2 228.5
Bridge - Integrated
PTP 600 Series 1.00 26.9 42 60.5 107.5 168.0
Connectorized
Table 6 - Lateral Force – Metric
Largest Surface Lateral Force (kg) at wind speed (m/s)

Area (sq m)
30 40 50 60 70
PTP 600 Series 0.130 12 22 34 49 66
Bridge - Integrated
PTP 600 Series- 0.093 9 16 24 35 48
Connectorized
NOTE
When the connectorized version of 600 Series bridge is used with external antennas,
the figures from the antenna manufacturer for lateral force should be included to
calculate to total loading on the mounting structure.
41
4.7.2 Capabilities of the PTP 600 Series Bridges
The structure and mounting brackets of the PTP Series systems are capable of withstanding
wind speeds up to 151mph (242 kph). The installer should ensure that the structure to which
the PTP 600 Series Bridge is fixed to is also capable of withstanding the prevalent wind
speeds and loads.
4.7.3 Wind Speed Statistics
Installers are recommended to contact the national meteorological office for the country
concerned to identify the likely wind speeds prevalent at the proposed location. This will
enable the installer to estimate the total wind loading on the support structures.
Examples of the sort of statistics that are available are:
USA - Reported Fastest Single Wind Velocities for Selected U.S. Cities
(Source: National Weather Service).

City, State Wind Velocity
(mph)
Bismarck, North Dakota 72
Buffalo, New York 91
Chicago, Illinois 87
Hatteras, North Carolina 110
Miami, Florida 132
New York, New York 99
Pensacola, Florida 114
UK Meteorological Office, www.meto.gov.uk
Peak wind speed contour maps can be found as Fig 3a/3b at:
http://www.meto.gov.uk/education/historic/1987.html
42
4.8 Path Loss Considerations

Path loss is the amount of attenuation the radio signal undergoes between the two ends of
the link.
4.8.1 Calculating Path Loss
The path loss is the sum of the attenuation of the path if there were no obstacles in the way
(Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a
margin to allow for possible fading of the radio signal (Fade Margin). The calculation of
Equation 2 needs to be performed to judge whether a particular link can be installed.
Equation 2 - Path Loss
L free _ space + Lexcess + L fade + Lseasonal < Lcapability

Where
Free Space Path Loss (dB)

L free _ space
Excess Path Loss (dB)
Lexcess
Fade Margin Required (dB)
L fade
Seasonal Fading (dB)
Lseasonal
Equipment Capability (dB)
Lcapability
4.8.2 Adaptive Modulation
Adaptive Modulation ensures that the highest throughput that can be achieved
instantaneously will be obtained, taking account of propagation and interference. When the
link has been installed, web pages provide information about the link loss currently measured
by the equipment, both instantaneously and averaged. The averaged value will require
maximum seasonal fading to be added, and then the radio reliability of the link can be
computed.
43
For minimum error rates on TDM links, the maximum modulation mode should be limited to
64QAM 0.75.
The values for (BPSK) are static receive sensitivity measurements. The other values are
static receive sensitivity measurements with an AMOD threshold applied. The AMOD
threshold applied is for a benign radio channel.
Field definitions are:
Sensitivity
Sensitivity is defined as the combined receive input signal level on both horizontal and vertical
-7
inputs that produces a Null BER Error ratio of 3x10 .
Output Power
The output power is for a centre channel in Region 1. The output power will be reduced on the
edge channels and may vary if different region codes are selected.
AMOD Threshold
The AMOD threshold is the combined receive input signal level on both horizontal and vertical
inputs that results in the link consistently entering the receive modulation mode under
consideration as the signal level is increased.
System Threshold
Thresholds for all modes except BPSK are for the relevant link optimization AMOD
thresholds. System threshold for BPSK is the RPSK receive sensitivity.
Max Link Loss
The maximum link loss for each modulation mode is derived from the AMOD threshold for that
mode (sensitivity threshold for BPSK) and the maximum Region 1 centre channel output
power. The figures assume integral antennas are used, with gain depending upon frequency
band as follows:
23 dBi (5.9 GHz, 5.8 GHz and 5.4 GHz)
22 dBi (4.8 GHz and 4.9 GHz)
21.5 dBi (4.5 GHz)
18 dBi (2.5 GHz)
4.9 System Threshold, Output Power and Link Loss

For details of the system threshold, output power and link loss for each frequency variant in
all modulation modes for all available channel bandwidths, refer to:
• Section 17.2.7 PTP 25600 System Threshold, Output Power and Link Loss
44
5 Lightning Protection
This section provides instructions for protecting PTP 600 installations against lightning strike.
The purpose of lightning protection is to protect structures, equipment and people against
lightning by conducting the lightning current to ground via a separate preferential solid path.

• 5.1 Lightning Protection Zones
• 5.2 LPU Configuration Options
• 5.3 LPU Kit
• 5.4 LPU Installation Wiring
• 5.5 LPU Installation Diagrams
This section should be treated as a guide only. The actual degree of lightning protection
required depends on local conditions and weather patterns and applicable local regulations.
Full details of lightning protection methods and requirements can be found in the international
standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No.
70-1984 or section 54 of the Canadian Electric Code.
CAUTION
EMD (Lightning) damage is not covered under standard warranty. The
recommendations in this user manual, when implemented correctly, give the user the
best protection from the harmful effects of EMD. However 100% protection is neither
implied nor possible.
5.1 Lightning Protection Zones

When the ODU is installed on a mast, tower or wall, it may be in one of two possible lightning
protection zones :
• Zone A: In this zone a direct lighting strike is possible. Do not mount the ODU in this
zone.
• Zone B: In this zone, direct EMD (Lightning) effects are still possible, but mounting in this
zone significantly reduces the possibility of a direct strike. Mount the ODU in this zone.
The zones are determined using the ‘rolling sphere method’: an imaginary sphere, typically 50
meter in radius, is rolled over the structure. All structure points that contact the sphere
indicate the zone (A) where a direct strike is possible. Similarly points that do not contact the
sphere indicate a zone (B) where a direct strike is less likely.
Zones A and B are shown in Figure 16.
45
Figure 16 - ODU mounted in Zones A & B
It may be possible to extend Zone B by installing a finial above the ODU (Figure 17).
Figure 17 – Using a Finial to extend Zone B
46
In Zone B, a direct lightning strike is unusual, but the un-attenuated electromagnetic field is
still present. Equipment mounted in Zone B should be grounded using grounding wire of at
least 10 AWG. This grounding wire should be connected to a grounding rod or the building
grounding system before entry in to building.
NOTE
Local regulations may also require the fitting of the 8 AWG grounding wire.
WARNING
Equipment mounted in Zone A must be capable of carrying the full lightning current.
Mounting of the ODU in Zone A is not recommended. Mounting in Zone A should only
be carried out observing the rules governing installations in Zone A. Failure to do so
may put structures, equipment and life at risk.
The PTP 600 Series bridge ODU grounding point can be found on the bottom of the unit. The
ODU is supplied with an appropriate grounding lug.
The following protection requirements are mandatory in both Zones A and B:

• The ODU must be earthed
• Screened CAT 5e cable must be used
• Surge arrestors of type PTP-LPU must be installed at both the ODU and building entry
• There must be an earth connection at building entry
The recommended standard components for protecting installations are listed in Section 5.5
LPU Installation Diagrams.
47
5.2 LPU Configuration Options

The PTP LPU can be installed in one of the following configurations:
• Option 1: Back-to-Back with the ODU using the supplied brackets delivered part of the
installation of a link. This is the configuration recommended by Motorola.
• Option 2: using the U-Bolt bracket supplied with the PTP LPU Kit.
Typical examples of these two configurations are shown in Figure 18 and Figure 19.
CAUTION
Grounding Points are shown unprotected for clarity. Grounding points should be
adequately weatherproofed to prevent corrosion and possible loss of ground
continuity.
Figure 18 – Example of PTP-LPU Configuration – Option 1 (Back-to-Back Recommended)
48
Figure 19 - PTP-LPU - Installation Option 2 (Using U-Bolt)
A second Lightning protection Unit should be mounted at the building entry point and must be
grounded.
49
5.3 LPU Kit

The PTP-LPU Kit is supplied with a 600mm ODU to PTP-LPU cable pre-fitted with glands.
Figure 20 shows all the components that are supplied with the Motorola Kit WB2907AA.
Figure 20 - PTP LPU Full Kit
The cable between the two lightning protection units (top and bottom) should be of the type
recommended by Motorola (Section 2.10 Cables and Connectors) and terminated as shown
in Figure 35.
50
5.4 LPU Installation Wiring

Figure 21 shows the correct installation wiring for a PTP 600 with lightning protection.
Figure 21 - Simplified Circuit Diagram
51
5.5 LPU Installation Diagrams

This section contains diagrams to show how the components of PTP 600 sites are installed
and connected with LPU. The diagrams cover the following configurations:
• Typical mast or tower installation
• Typical wall installation
• Mast or tower installation with E1/T1
• Wall installation with E1/T1
• Mast or tower installation with GPS Sync Unit
• Wall installation with GPS Sync Unit
• Mast or tower installation with GPS Sync Unit and E1/T1
• Wall installation with GPS Sync Unit and E1/T1
The recommended standard components for protecting installations are:

• Screened CAT 5e cable, also known as Shielded CAT 5e or CAT 5e STP (Shielded
Twisted Pair)
• Surge arrestor, type PTP-LPU: 4 or 8 per link (2 or 4 Motorola Kits Part Number
WB2907AA)
• Grounding stake
• Grounding cable: minimum size 8 AWG, preferably 6 or 4 AWG
• RJ45 screened connectors
Additional components are listed under each diagram where required. The recommended
cables are specified in Section 2.10 Cables and Connectors.
There may be a local regulatory requirement to cross bond the CAT 5e cable to the mast or
tower at intervals as regular as every 10 meters (33 feet). This can be achieved using an
Andrew grounding assembly type 223158 or similar.
NOTE
Refer to instructions contained in the Andrew grounding kit for correct installation, or if
instructions are missing, refer to:
http://awapps.commscope.com/catalog/product_details.aspx?id=15832&tab=2
Where an installation already has, or requires the use of a Master Ground Bar then the
requirements of Motorola Specification R56: STANDARDS AND GUIDELINES FOR
COMMUNICATION SITES (68P81089E50) take precedence over those in this guide.
52
NOTE
If a coaxial (or other) cable is already cross-bonded to the mast or tower, the same
cross bonding points on the mast or tower must be used for the CAT 5e cable.
5.5.1 Typical Mast or Tower Installation
Figure 22 shows a typical PTP 600 Series Mast or Tower installation using PTP-LPU Surge
protection for a configuration without a GPS Sync Unit or E1/T1 ports. This installation
requires 4 Motorola PTP-LPU Surge Arrestors (2 kits).
Figure 22 - Typical Mast or Tower Installation
53
5.5.2 Typical Wall Installation
Figure 23 shows a typical PTP 600 Series Wall installation using PTP-LPU Surge protection
for a configuration without a GPS Sync Unit or E1/T1 ports. This installation requires 4
Motorola PTP-LPU Surge Arrestors (2 kits).
Figure 23 - Typical Wall Installation
54
5.5.3 Mast or Tower Installation with E1/T1
Figure 24 shows a typical PTP 600 Series Mast or Tower installation using PTP-LPU Surge
protection for a configuration that includes E1/T1 ports. This installation requires 8 Motorola
PTP-LPU Surge Arrestors (4 kits).
Figure 24 – Mast or Tower Installation with E1/T1
55
5.5.4 Wall Installation with E1/T1
Figure 25 shows a PTP 600 Series Wall installation using PTP-LPU Surge protection for a
configuration that includes E1/T1 ports. This installation requires 8 Motorola PTP-LPU Surge
Arrestors (4 kits).
Figure 25 - Wall Installation with E1/T1
56
5.5.5 Mast or Tower Installation with GPS Sync Unit
Figure 26 shows a PTP 600 Series Mast or Tower installation using PTP-LPU Surge
protection for a configuration that includes a GPS Sync Unit. This installation requires 4
Motorola PTP-LPU Surge Arrestors (2 kits). This installation also requires: GPS Sync Unit
from MemoryLinkl – 1 per link (1 Motorola kit).
Figure 26 – Mast or Tower Installation with GPS Sync Unit
57
5.5.6 Wall Installation with GPS Sync Unit
configuration that includes a GPS Sync Unit. This installation requires 4 Motorola PTP-LPU
Surge Arrestors (2 kits). This installation also requires: GPS Sync Unit from MemoryLinkl – 1
per link (1 Motorola kit).
Figure 27 –Wall Installation with GPS Sync Unit
58
5.5.7 Mast or Tower Installation with GPS Sync Unit and E1/T1
Figure 28 shows a PTP 600 Series Mast or Tower installation using PTP-LPU Surge
protection for a configuration that includes a GPS Sync Unit and E1/T1 ports. This installation
requires 8 Motorola PTP-LPU Surge Arrestors (4 kits). This installation also requires: GPS
Sync Unit from MemoryLinkl – 1 per link (1 Motorola kit).
Figure 28 - Mast or Tower Installation with GPS Sync Unit and E1/T1
59
5.5.8 Wall Installation with GPS Sync Unit and E1/T1
configuration that includes a GPS Sync Unit and E1/T1 ports. This installation requires 8
Motorola PTP-LPU Surge Arrestors (4 kits). This installation also requires: GPS Sync Unit
from MemoryLinkl – 1 per link (1 Motorola kit).
Figure 29 - Wall Installation with GPS Sync Unit and E1/T1
60
6 Installation
6 Installation
This section provides instructions for installing a PTP 600 link.
It is advised that the link be configured and tested on a bench before the final installation of
the units on site. Providing it is safe to do so, the installer should take the bench testing
process to the point where a radio link is established. For more information, see the PTP 600
Series Deployment Guide.
CAUTION
Motorola recommends that only qualified personnel undertake the installation of a
PTP 600 Series Bridge solution.
We recommend that the practices and procedures detailed in the Motorola manual
R56 "STANDARDS AND GUIDELINES FOR COMMUNICATION SITES"
(68P81089E50) be applied to all new site build activities. This manual is provided on
the PTP 600 CD-ROM.
The standard PTP 600 Series installation procedure consists of the following stages:
1. Prepare for installation as described in Section 6.3 Preparation.
2. Mount the ODUs as described in Section 6.4 Mounting the ODUs.
3. Connect the equipment as described in Section 6.5 Connecting Up.
4. Establish a radio link as described in Section 6.6 Establishing a Radio Link.
Depending upon the options required, see also the following sections:
1. If a connectorized PTP 600 variant is to be installed, see Section 10 Connectorized

PTP 600 Series Bridge.
2. If TDD synchronization is required, see Section 11 TDD Synchronization Installation

and Configuration.
3. If an E1/T1 link is to be installed, see Section 12 E1/T1 Installation Guide.
4. If the link is to be encrypted, see Section 14 AES Encryption.
61
6 Installation
6.1 Installation Support

Online installation support and contact details for your regional support can be found at
http://www.motorola.com/ptp
A Frequently Asked Questions (FAQ) section can be found in Section 18 FAQs.
6.2 Legal Disclaimer

IN NO EVENT SHALL MOTOROLA, INC. BE LIABLE FOR ANY INJURY TO ANY PERSONS
OR ANY DAMAGE CAUSED DURING THE INSTALLATION OF THE MOTOROLA PTP 600
SERIES PRODUCT.
6.3 Preparation
6.3.1 Checks
Before proceeding with the installation, perform the following checks:

• Ensure that you have planned the link, as described in Section 4 Planning
Considerations.
• Check the contents of all packages against the parts lists shown in the packing list.
• Ensure that you are qualified to undertake the work.
• Ensure that you have taken the correct safety precautions.
6.3.2 Tools Required
The following specific tools are required to install a PTP 600 Series Bridge, in addition to
general tools:
• 13mm wrench and 22 mm wrench for use with the glands
• RJ45 crimp tool (it must be the correct tool for the type of RJ45 being used)
• Personal Computer (PC) with 10, 100 or 1000 BaseT Ethernet
• Either Internet Explorer version 6 or higher, or FireFox 2.0 or higher are recommended.
• Ethernet patch cables
• Motorola PTP LINKPlanner report for this link
62
6 Installation
6.4 Mounting the ODUs
6.4.1 Mounting Bracket

The ODU is pre-fitted with a mounting bracket (designed to ease installation) and with earth bonding
leads (Figure 30).
Figure 30 – ODU with Mounting Bracket and Earth Bonding Leads
6.4.1.1 Safety Precautions When Mounting the ODU
WARNING
To prevent failure of the assembly, observe the precautions listed below when
mounting the ODU.
The following safety precautions must be taken when mounting the ODU:
• Do not remove the pre-fitted mounting bracket from the ODU.
• Do not mount the ODU on poles with diameter less than 50mm (2”) or greater than 75mm
(3”). The ODU mounting bracket is designed to work only with poles with diameter in the
50 mm (2”) to 75 mm (3”) range.
• Do not over-tighten the bolts.
63
6 Installation
6.4.2 ODU Mounting Procedure
The ODU must be mounted using the following steps, ensuring that the cable entry is at the
bottom:
1. Attach the bracket strap to the pole using M8 x 70 mm bolts, M8 flat washers and M8
coil washers (Figure 31). Tighten to ensure the assembly grips but can be adjusted.
Figure 31 – ODU Bracket Strap
2. Offer the ODU (with pre-fitted mounting bracket) to the bracket strap and affix using
the captive M8 bolt. Tighten to ensure the assembly grips, but can be adjusted on the
pole (Figure 32 and Figure 33).
Figure 32 – ODU Mounting Bracket
64
6 Installation
Figure 33 - ODU Mounted on Pole
3. Adjust the elevation and azimuth of the unit before tightening to the required torque
settings of 14 Nm (11 lb ft) for both bolts.
CAUTION
Attach the free end of one earth bonding lead (large tag M10) to the tower metal
work. On no account must this be attached to the mounting bracket bolts.
The enclosure and mounting brackets of the PTP 600 Series Bridge product range are
capable of withstanding wind speeds up to 151mph (242kph). The installer should ensure that
the structure the bridge is fixed to is also capable of withstanding the prevalent wind speeds
and loads. See Section 4.7 Wind Loading.
65
6 Installation
6.4.3 Hoist and Safety Loop
Use the integral safety loop (Figure 34) for hoisting the ODU up a mast, tower or building.
When the ODU is in position, use the safety loop as a fixing point to secure a permanent
lanyard from the mast, tower or building to the ODU, as a precaution against mounting failure.
Figure 34 - Integral Safety Loop
WARNING
The safety lanyard must not exceed 1m (approx 3 ft) in length. The lanyard must be
made from a material that does not degrade in an outdoor environment.
The safety lanyard must be fixed to a separate fixing point that is not part of the direct
mounting system for the ODU.
If the safety loop or its fixing is damaged in any way or has been exposed to a shock
loading due to a fall, replace it with a new one before undertaking any further
operations.
66
6 Installation
6.5 Connecting Up
6.5.1 Preparing the PIDU Plus To ODU Cable
The maximum cable length between the ODU and the user’s Network Equipment is 100m
(330 ft). Cable lengths up to 300m (984 ft) can be used where the PIDU Plus to ODU cable is
supplying power only, that is, when using the PTP 600 Series Bridge Optical Interface.
6.5.1.1 Cable Safety Precautions
WARNING
The copper screen of the recommended Superior Essex cable is very sharp and may
cause personal injury. When preparing the Superior Essex cable, take the following
safety precautions:
ALWAYS wear cut resistant gloves (check the label to ensure they are cut
resistant).
ALWAYS wear protective eyewear.
ALWAYS use a rotary blade tool to strip the cable (DO NOT use a bladed knife).
To use the rotary blade tool, fit it around the outer cable sheaf and rotate the cutter
around the cable once or twice. The stripped outer section can then be removed.
67
6 Installation
6.5.1.2 Cable Assembly
The cable should be assembled as shown in Figure 35:
Figure 35 - Correct Cable Preparation for the Recommended Cable
68
6 Installation
CAUTION
Check that the crimp tool matches the RJ45 connector being used.
Both ends of the ODU cable are terminated in the same way. The above procedure should be
repeated for the PIDU Plus end of the cable when the cable routing process is complete. This
assumes that the installation uses PTP LPUs. If not, then the PIDU Plus end of the cable
does not require a Gland, but just the RJ45.
NOTE
The PIDU Plus end of the cable does not employ a cable gland.
Figure 36 shows a completed ODU to PIDU Plus cable.
Figure 36 - Completed ODU Connector
CAUTION
Do not over tighten the glands as the internal seal and structure may be damaged.
See Figure 37 for an example of an over tightened cable gland.
Figure 37 - Correct and Incorrect Tightening of Cable Gland
69
6 Installation
6.5.2 Making the Connections at the ODU
Looking at the back of the unit with the cable entry at the bottom, the PIDU Plus connection is
the first hole on the right (Figure 38) and is labeled “PIDU Plus +”.
Figure 38 – ODU PIDU Plus Connexion
70
6 Installation
6.5.3 Making the PIDU Plus Connection At The ODU
The procedure for connecting the PIDU Plus cable to the ODU is described in Figure 39. It is
often easier to carry out this procedure on the ground or a suitable surface prior to mounting
the ODU.
Ensure that no power is connected to the PIDU Plus or present on the cable before
connecting the ODU.
Figure 39 - Connecting the PIDU Plus+ to the ODU
Step 1: Assemble the cable as described in Step 2: Insert the RJ45 connector making
6.5.1 above sure that the locking tab snaps home
Step 3: Screw in the body of the weather

proofing gland and tighten
Step 4: Screw on the clamping nut and tighten
(Do not over tighten – see Figure 37)
71
6 Installation
Should it be necessary to disconnect the PIDU Plus to ODU cable at the ODU, this can be
achieved by removing the weather proofing gland and depressing the RJ45 locking tab with a
small screwdriver as shown below.
Figure 40 - Disconnecting the ODU
CAUTION
To prevent damage to the ODU while making or breaking the connection, ensure that
power is removed from the system at the PIDU Plus.
6.5.4 Routing the Cable
After connecting the cable to the ODU it can be routed and secured using standard cable
routing and securing techniques. When the cable is in place it can then be cut to the desired
length at the PIDU Plus prior to connection to the PIDU Plus.
6.5.5 Fitting a Lightning Protection Unit
If you have opted to fit a Lightning Protection unit, this should be installed by following the
manufacturer’s instruction. For recommended types see Section 5 Lightning Protection.
72
6 Installation
6.5.6 Grounding the Installation
The Outdoor Unit (ODU) must be properly grounded to protect against power surges. It is the
user’s responsibility to install the equipment in accordance with Section 810 of the National
Electric Code, ANSI/NFPA No.70-1984 or Section 54 of the National Electrical Code in the
country of installation. These codes describe correct installation procedures for grounding the
outdoor unit, mast, lead-in wire and discharge unit, size of grounding conductors and
connection requirements for grounding electrodes. It is recommended that installation of the
outdoor unit be contracted to a professional installer.
6.5.7 Making the ODU Connection at the PIDU Plus
The procedure for connecting the RJ45 from the ODU to the PIDU Plus is described in Figure
41. The ODU is connected to the PIDU Plus by means of a concealed RJ45 connector. The
RJ45 connection has been placed inside the PIDU Plus hinged cover to prevent the user from
inadvertently plugging other equipment into the ODU RJ45 socket.
CAUTION
Plugging other equipment into the ODU RJ45 socket may damage the equipment due
to the non-standard techniques employed to inject DC power into the 1000BaseT
connection between the PIDU Plus and the ODU. Plugging the ODU into other
equipment may damage the ODU and/or the other equipment.
73
6 Installation
Figure 41 - Connecting the ODU to the PIDU Plus+
Step 1: Undo the retaining screw and hinge back the cover.
Step 2: Plug in the ODU into the PIDU Plus Cable ensuring that it snaps
home.
Step 3: Replace the cover and secure with the retaining screw.
74
6 Installation
6.5.8 Making the Network Connection at the PIDU Plus
The Network connection is made by connecting the user’s Network Equipment directly to the
PIDU Plus LAN port as shown in Figure 42.
Figure 42 - Making the Network Connection at the PIDU Plus
6.5.9 Mounting the PIDU Plus
Motorola recommends that you mount the PIDU Plus on a wall or other suitable mounting
surface (but this is optional. This prevents the unit from being knocked or kicked and can help
maintain link availability. Ensure that the Recovery switch can be accessed when mounting
the unit.
The procedure for mounting the PIDU Plus is described in Figure 43.
75
6 Installation
Figure 43 - Mounting the PIDU Plus
Step 1: Fix the PIDU Plus to the wall using the lugs provided.
Step 2: Make connections as per Section 6.5.7 Making the ODU

Connection at the PIDU Plus.
76
6 Installation
CAUTION
Do not dress the RJ45 cables too tightly, as this may make the connections
unreliable. Figure 44 shoes the correct and incorrect ways to dress RJ45 cables
when connected to the PIDU Plus.
Figure 44 - Correct and Incorrect RJ45 Cable Dressing
CAUTION
The PIDU Plus is not waterproof and should be mounted away from sources of
moisture. If mounted outdoors, the unit should be mounted in a rain proof enclosure,
preferably ventilated.
It is also recommended that you fit a drip loop on the PIDU Plus to ODU cable to ensure that
any moisture that runs down the cable into the cabinet or enclosure cannot enter the PIDU
Plus. This is shown in Figure 45. The network connection and mains cable should be treated
in the same way if there is a risk that they can carry moisture to the PIDU Plus.
77
6 Installation
Figure 45 – PIDU Plus Drip Loop Configuration
CAUTION
It is possible for moisture to enter the cable due to damage to the outer protective
layer. This moisture can track down the inside of the cable, filling up the drip loop and
eventually finding its way into the PIDU Plus. To protect against this the outer
protective layer of the cable can be opened up at the bottom of the drip loop to allow
this moisture to escape.
78
6 Installation
6.5.10 Powering Up
The PTP 600 Series Bridge is supplied as a pair of matched Master/Slave units. The Master
unit can now be powered up and accessed using the default URL http://169.254.1.2/; the
Slave unit can be accessed using http://169.254.1.1/.
Prior to powering up the PTP 600 Series Bridge, a computer with web browsing capabilities
should be configured with an IP address of 169.254.n.n and subnet mask of 255.255.0.0
where n is any value between 1 and 254 but excluding 1.1 or 1.2. If the default addresses of
the unit 169.254.1.1/2 clashes with an address you are already using on your LAN, or you are
not sure, you should set up an isolated LAN. As the LAN connection presented at the PIDU
Plus has a default configuration as a hub/switch (and auto-sensing MDI/MDIX cross over is
employed), connection can be made directly to the computer using a standard CAT 5 patch
cable.
NOTE
It is possible that some units may not be accessed using the above default URL. This
is because these units may have been previously configured with IP addresses
10.10.10.11 (Master) and 10.10.10.10 (Slave). Therefore, users must use the URL
http://10.10.10.10/ and/or URL http://10.10.10.11/ to configure the units. Please
ensure that a computer with web browsing capabilities is configured with an IP
address of 10.10.10.n, where n is any value between 2 and 254 but excluding 10 and
11, to configure these units.
79
6 Installation
6.6 Establishing a Radio Link

The following is a description of the steps taken to establish a radio link between the two
units forming the bridge and align the units for the best signal strength.
6.6.1 Aligning the PTP 600 Series Bridge ODUs
The PTP 600 Series Bridge uses audible tones during installation to assist the installer with
alignment. The installer should adjust the alignment of the ODU in both azimuth and elevation
.
until highest pitch tone is achieved
The pitch of the alignment tone is proportional to the received power of the wireless signals.
The best results are usually achieved by making small incremental movement in angular
alignment.
The tones and their meanings are as follows:
Table 7 - Audio indications from the ODU
State Name Tone State Description Pitch Indication (Higher

Description pitch = higher power)
Free Channel Regular beep Executing band scan N/A

Search
Scanning Slow broken Not demodulating the wanted Rx Power

tone signal
Synchronized Fast broken Demodulating the wanted Rx Power

tone signal
Registered Solid tone Both Master and Slave units Rx Power

exchanging Radio layer MAC
management messages
Alarm Fast broken A fatal error has occurred.

dual tone
The term ‘wanted signal’ refers to that of the peer unit being installed.
In each of the states detailed above, the unit should be aligned to give the highest pitch tone.
It should be noted that if, when in the Synchronized or Registered state, the tone varies
wildly, you may be suffering from interference or a fast fading link. Installing in this situation
may not give a reliable link. The cause of the problem should be investigated.
80
6 Installation
For the ease of alignment, both Master and Slave units use the install tones in the same way
but with some small behavioral differences. This allows the installer to install the Slave unit
first and carry out the initial alignment with the Master unit if desired. However, due to the
behavioral differences of Master and Slave units, it is recommended that the Master unit is
installed first and the initial alignment carried out at the Slave unit.
Once the optimum performance has been achieved by directing the Slave unit (indicated by
highest frequency of tone) then adjustment of the direction of the Master unit should be done
without moving the Slave. Repeat if necessary at the Slave and then the Master until optimum
alignment has been obtained.
There is a graphical installation screen (section 7.7.8 Graphical Install) available using the
web interface that displays the state of the link during the alignment process (up = green,
down = red).
6.6.2 Behaviour During Installation
The following behavior should be noted:

• Band scan: When first started up and from time to time, the Master unit will carry out a
band scan to determine which channels are not in use. During this time, between 10 and
15 seconds, the Master unit will not transmit and as a consequence of this neither will the
Slave unit. During this time the installation tone on the master unit will drop back to the
band scan state, and the Slave unit will drop back to the Scanning state with the pitch of
the tone set to the background noise level. Alignment of the unit should cease during this
time.
• Radar detection: If the unit is operating where mandatory radar avoidance algorithms
are implemented, the ranging behaviour for the PTP 600 Series Bridge may be affected.
The Master has to monitor the initially chosen channel for 60 seconds to make sure it is
clear of radar signals before transmitting. If a radar is detected during any of the
installation phases, a further compulsory 60 seconds channel scan will take place as the
master unit attempts to locate a new channel that is free of radar interference.
• Ranging: The Master unit can take up to 60 seconds in 0-40km (0-25 miles) mode, 90
seconds in 0-130km (0-81 miles) mode and 120 seconds in 0-200km (0-124 miles) mode
to determine the range of the link being installed. The Master unit will remain in the
Scanning state until the range of the link has been established. The Master unit will only
move to the Synchronized state when the range of the link has been established.
81
6 Installation
• Retrying same channel: If, at the end of the ranging period, the Registered state is not
achieved due to interference or other reasons, the Master unit will retry twice more on the
same channel before moving to another available channel. Should this occur it might take
a number of minutes to establish a link in the Registered state.
• Slave unit: The Slave unit does not have a ranging process. The slave unit will change to
the Synchronized state as soon as the wanted signal is demodulated.
6.6.3 Adjust Power Settings
The transmit power levels of the installed units must be adjusted to ensure they are not too
high. Excessive power levels may cause saturation of the receivers or false radar detection
(in radar enabled regions), leading to degradation of link performance and link failure.
To adjust power levels, follow this procedure:
1. Consult the report generated by the LINKPlanner tool and note the Transmit power
recommended levels.
2. Set the local unit power equal to the “LOCAL - Max Transmit Power setting while
pointing” value from the LINKPlanner report.
3. Set the remote unit power equal to the “REMOTE - Max Transmit Power setting while
pointing” value from the LINKPlanner report.
4. Access each unit separately.
5. Align the units.
6. Repeat Step 2 and 3 using the values “LOCAL - Max Transmit Power setting before
disarm” and “REMOTE - Max Transmit Power setting before disarm” , if different
than the corresponding “while pointing” values.
7. Reboot the local unit then reboot the remote unit.
8. Disarm the units.
82
6 Installation
6.6.4 Disarm on Completion
When the alignment process is complete, the installer MUST REMEMBER TO DISARM
BOTH UNITS in the link, as described in Section 7.7 Installation. This is necessary in order
to:
• Turn off the audible alignment aid (Section 7.7.7 Disarm Installation)
• Enable Adaptive Modulation
• Fully enable Advanced Spectrum Management with i-DFS
• Clear unwanted installation information from the various systems statistics
• Store the link range for fast link acquisition on link drop
• Enable higher data rates
NOTE
After 24 hours, the units will be disarmed automatically, provided that they are armed
and that the link is UP.
83
7 Web Page Reference
This section describes the PTP 600 web user interface and provides instructions for
operators.
The following topics describe the menu navigation bar and main menu options:
• 7.1 Menu Navigation Bar
• 7.2 Home (System Summary)
• 7.3 System Status
• 7.4 System Administration
The following topics describe the System Administration menu options:

• 7.5 Configuration
• 7.6 Statistics
• 7.7 Installation
• 7.8 Software Upgrade
• 7.9 Spectrum Management
• 7.10 Remote Management
• 7.11 Diagnostics Plotter
• 7.12 Change Password
• 7.13 License Key
• 7.14 Properties
• 7.15 Reboot
NOTE
The web pages are best viewed using a screen resolution of at least 1024 x 768
pixels on a PC using Microsoft Internet Explorer Version 6 or 7.
The web pages have also been tested with Firefox 2.0.0.12. Other browsers have not
been tested.
7.1 Menu Navigation Bar

The navigation bar on the left hand side of the web page is used to move between the various
management pages. The currently selected page is always highlighted with a light blue
background. The menu is hierarchical. Selecting a menu item which has associated submenu
options will automatically display all sub options. A sample web page with the navigation
menu is shown in Figure 46.
84
Figure 46 - Menu Navigation Bar
The web user interface menu has three main options.

• Home: This presents to the operator a high level summary of the PTP 600 Series Bridge
point-to-point wireless link.
• Status: This presents a more detailed set of system parameters describing the
performance of the wireless link together with other key system performance metrics.
• System Administration: This section is password protected and allows the system
administrator to perform all the day-to-day administrative procedures, for example
software upgrade and configuration changes.
85
7.2 Home (System Summary)

The home page for the PTP 600 Series Bridge (Figure 47) displays a high level summary of
the status of the wireless link and associated equipment.
Figure 47 - System Summary Page
The home page normally displays four key system attributes:
Wireless Link Status

The Wireless Link Status attribute displays the current status of the PTP 600 Series Bridge
wireless link. A state of ‘Up’ on a green background indicates that a point-to-point link is
established. A state of ‘Down’ on a red background indicates that the wireless link is not
established. If the link is down for an unknown reason the system administrator should first
consult the status web page for a more detailed summary of up to date system diagnostics.
Link Name
The link name attribute is a name and/or handle allocated by the system administrator to aid
the identification of the unit, network or building.
Elapsed Time Indicator
The elapsed time indicator attribute presents the total time in days, hours, minutes and
seconds since the last system restart. The system can restart for several reasons, for
example, commanded reboot from the system reboot webpage, or a power cycle of the
equipment.
System Clock
If SNTP (Simple Network Time Protocol) is enabled, or the clock has been set, then a system
clock attribute is displayed giving the date and time of the last page refresh. Section 7.10.8
SNTP (Simple Network Time Protocol) explains how to enable SNTP and Section 7.10.9
Setting the clock explains how to set the clock.
86
7.2.1 Home Page Alarm Display
The home page is also used to display all outstanding major system alarms. Whenever
system alarms are asserted, a yellow warning triangle is displayed on web page navigation
bar. The warning triangle will be visible from all web pages. Clicking the warning triangle will
cause the web page to jump back to the system homepage. Figure 48 shows a sample alarm
screen.
Figure 48 - Alarm Warning Triangle
87
7.2.2 System Alarms
The following system alarms are defined:
Ethernet Link Status

Current status of the Ethernet link. If there are any problems with the Ethernet interface, this
alarm will be asserted. This alarm will most likely be seen if the unit has no Ethernet cable
plugged into its Ethernet socket. Note that a change of state may generate an SNMP trap
and/or SMTP email alert.
Telecoms Channel Status
Indicates an alarm condition on a telecoms channel. Alarm conditions are listed in Table 8.
Table 8 – Telecoms Channel Status Alarm Conditions
Alarm Condition Meaning
No Signal (Local) There is no telecoms signal present at the
connection to the ODU at the local end.
No Signal (Remote) There is an absence of telecoms data across the
wireless link.
No Signal (Local and The above two alarm conditions occur concurrently.
Remote)
Remote Timing There is insufficient wireless capacity available to
carry telecoms data. Under these conditions
telecoms timing information is still sent to keep the
telecoms clocks synchronized.
No Signal (Local) and Indicates both no local signal and remote timing.
Remote Timing
In remote timing mode the ODU will transmit an Alarm Indication Signal (AIS), consisting of
all-ones, from the associated telecoms interface. A change of state may generate an SNMP
trap and/or SMTP email alert.
See Section 7.7.4.1 Telecoms Interface for a description of the Telecoms Interface.
Telecoms Interface A/B Loopback
The loopback status of telecoms channel A and B. These are intended for installation testing
and should be set to 'None' for normal operation. The wire connections to a unit can be tested
by applying a 'Copper' loopback to the local unit. The wireless connection to the remote unit
can be tested by applying a 'Wireless' loopback to the remote unit with no loopback on the
local unit.
A change of state may generate an SNMP trap and/or SMTP email alert. The loopback can
be disabled from the telecoms configuration sub menu (see Section 7.5.5 Telecoms
Configuration).
See Section 7.7.4.1 Telecoms Interface for a description of the Telecoms Interface.
Region Code
The region code prohibits the wireless unit from operating outside the regulated limits. An
invalid region code indicates a corrupted license key. Note that a change of state may
generate an SNMP trap and/or SMTP email alert.
88
Install Status
A non-OK value indicates that signaling was received with the wrong MAC address. Note that
it is very unusual to detect this, because units with wrongly configured Target MAC Address
will normally fail to establish a wireless link. However, rare circumstances may establish a
partial wireless link and detect this situation. NB: A non-OK value on start-up, or a change of
value during operation, may generate an SNMP trap and/or SMTP email alert.
Install Arm State
This alarm warns when a wireless unit is in installation mode. After installation the wireless
unit should be disarmed. This will increase the wireless link’s data-carrying capacity and stop
the installation tone generator. The wireless link is disarmed from the ‘Installation’ process
see Section 7.7.7 Disarm. A change of state may generate an SNMP trap and/or SMTP email
alert.
Unit Out Of Calibration
The unit is out of calibration and must be returned to the factory using the RMA process for
re-calibration.
Encryption Enable Mismatch
Encryption has been enabled on one end of the wireless link but not the other. For more
information, see Section 14 AES Encryption.
Incompatible Region Codes
The PTP 600 Series Bridge uses region codes to comply with local regulatory requirements
governing the transmission of wireless signals in the frequency bands in which it operates.
Region codes can only be changed by obtaining a new PTP 600 Series license key. If this
alarm is encountered, the appropriate license keys from the country of operation should be
obtained from your distributor. Applying license keys containing the same region codes to
both ends of the link will remove the alarm. A change of state may generate an SNMP trap
No Wireless Channel Available
Spectrum Management was unable to locate a suitable wireless channel to operate on. Note
that a change of state may generate an SNMP trap and/or SMTP email alert.
Wireless Link Disable Warning
This warning is displayed if the Wireless link has been administratively disabled via the SNMP
Interface (see Section 7.10 Remote Management). The Wireless Interface MIB-II
ifAdminStatus attribute has been set to DOWN. To enable the Ethernet interface, set the
ifAdminStatus attribute to UP. Note that a change of state may generate an SNMP trap and/or
SMTP email alert.
Ethernet Link Disable Warning
This warning is displayed if the Ethernet link has been administratively disabled via the SNMP
Interface (see Section 7.10 Remote Management). The Ethernet Interface MIB-II
ifAdminStatus attribute has been set to DOWN. To enable the Ethernet interface, set the
ifAdminStatus attribute to UP. Note that a change of state may generate an SNMP trap and/or
SMTP email alert.
Fiber Link Status
If the fiber link is not OK, there are two possible causes: Either the fiber link has been installed
but disabled (because the license key does not include fiber support), or the link could not be
established even though an optical carrier was detected (due perhaps to a broken TX fiber, or
the link is disabled at the fiber link partner). Note that a change of status may generate an
SNMP trap and/or SMTP email alert.
89
Ethernet Configuration Mismatch Alarm

The detection of Ethernet fragments (runt packets) when the link is in full duplex is an
indication of an auto-negotiation or forced configuration mismatch. Note that a change of state
may generate an SNMP trap and/or SMTP email alert.
Incompatible Master and Slave
A non-zero value indicates that the master and slave ends of the wireless link are different
hardware products, or have different software versions. Note that it is very unusual to detect
this because incompatible units will normally fail to establish a wireless link. However, some
combinations may establish a partial wireless link and detect this situation. Note that a non-
zero value may generate an SNMP trap and/or SMTP email alert.
TDD Synchronization Status
Current status of the TDD Synchronization (OK, Timing System Failure, Not Synchronized).
Note that a change of state may generate an SNMP trap and/or SMTP email alert.
SNTP Synchronization failed
This warning indicates that SNTP has been enabled but that the unit is unable to synchronize
with the specified SNTP server. Section 7.10.8 SNTP (Simple Network Time Protocol)
explains how to configure SNTP. Note that a change of state may generate an SNMP trap
90
7.3 System Status

The status page (Figure 49) gives the system administrator a detailed view of the operation of
the PTP 600 Series Bridge from both the wireless and network perspectives.
Figure 49 - Status Page
The page is subdivided into five categories:

• Equipment: This contains the unit’s inventory and identification information.
• Wireless: This presents the key wireless metrics, which are displayed as a series of
measurements.
• Ethernet/Internet: This describes the unit’s network identity and connectivity.
• Telecoms: This describes the unit’s E1/T1 telecoms interface parameters.
• TDD Synchronization: This shows the status of TDD synchronization.
The status page can be configured to refresh itself at an operator defined rate (if the user is
logged in as system administrator). The refresh period defaults to 3600 seconds and can
easily be changed to refresh at any period between 2 seconds and 3600 seconds. Pressing
the ‘Update Page Refresh Period’ button causes a new page refresh period to be adopted by
the system. The page refresh mechanism uses a HTML Meta refresh command. Therefore
the refresh is always initiated by the local browser and not by the PTP 600 Series Bridge at
this interval.
91
The two PTP 600 Series bridges units are arranged in a master and slave relationship. The
roles of the units in this relationship are displayed in the page title. The master unit will always
have the title ‘- Master’, and the slave will always have ‘- Slave’ appended to the ‘Systems
Status’ page title.
The following attributes are displayed on the status page:
Link Name
The link name is allocated by the system administrator and is used to identify the equipment
on the network. The link name attribute is limited to a maximum size of 63 ASCII characters.
Link Location
The link location is allocated by the system administrator and can be used as a generic
scratch pad to describe the location of the equipment or any other equipment related notes.
The link location attribute is limited to a maximum size of 63 ASCII characters.
Software Version
The attribute describes the version of software installed on the equipment. The format of the
attributes is FFSSS-XX-YY where FF is the frequency variant (2.5, 4.5, 5.4, 5.8 or 5.9 GHz),
SSS is the System Release, XX is the major release version and YY is the minor release
version.
Hardware Version
The hardware version attribute contains all the combined hardware version information. The
attribute is formatted as DXX-RYY-Z where DXX contain the version of the digital card, RYY
contains the version of the RF (radio frequency) card and Z describes the antenna type which
can be I (integrated) or C (connectorized).
Region Code
The region code is used by the system to constrain the wireless to operate within regulatory
regime of the particular country. The region code is encoded in the product license key. If the
operator wishes to change region code, a new license key must be obtained from Motorola or
the local point-to-point distributor / system integrator.
Elapsed Time Indicator
The elapsed time indicator attribute presents the total time in years, days, hours, minutes and
seconds since the last system restart. The system can restart for several reasons, for
example commanded reboot from the system reboot web page, or a power cycle of the
equipment.
Ethernet Link Status:
Current status of the Ethernet link. A state of ‘Up’ with a green background indicates that an
Ethernet link is established. A state of ‘Down’ with a red background indicates that the
Ethernet link is not established.
Ethernet Speed and Duplex
The negotiated speed and duplex setting of the Ethernet interface. The speed setting is
specified in Mbps.
Full Duplex data transmission means that data can be transmitted in both directions on a
signal carrier at the same time. For example, on a local area network with a technology that
has full duplex transmission; one workstation can be sending data on the line while another
workstation is receiving data.
92
Half Duplex data transmission means that data can be transmitted in both directions on a
signal carrier, but not at the same time. For example, on a local area network using a
technology that has half duplex transmission, one workstation can send data on the line and
then immediately receive data on the line from the same direction in which data was just
transmitted.
Remote IP Address
Hyperlink to the other side of the Link. The IP address of the peer link is displayed if the Link
is UP, otherwise “unavailable” is displayed.
Telecoms Channel A and B
Indicate the current status of the telecoms channels. Channels which are disabled during
installation are marked as such. Correctly operating channels display "Up" on a green
background, but alarm conditions (described in Section 7.2.1 Home Page Alarm Display)
have a red background.
The Telecoms Latency value, displayed in microseconds, is determined when the wireless
link starts and will remain the same for a given wireless configuration. Section 3.10 Telecoms
Circuits describes methods for reducing telecoms latency on links which support high data
rate modulation modes.
Under normal circumstances the unit will freely transition between modulation modes to suit
the wireless conditions. The "Single Payload Lock" indicates that the ODU will prevent
transitions from Single Payload modes to the higher Dual Payload modes in order to avoid
loss of telecoms data. This field appears where such a transition would pass through modes
which cannot carry telecoms data. This may be because, in order to control latency, the
lowest modulation mode has been set to a higher Single Payload mode.
In the absence of the Single Payload Lock the wireless will transition to the faster Dual
Payload modes as soon as the conditions are appropriate. With the lock enabled, the wireless
will dwell in slower Single Payload modes whenever there are operational telecoms links
(operational links are shown as "Up" in the telecoms channel field described above). When
the lock is actively preventing transitions, the value displayed changes from "Enabled" to
"Applied".
TDD Synchronization
Displays the TDD Synchronization status for the link. For more information, refer to Section
11.3.4 TDD Synchronization Status.
Refresh Page Period
The Status page refreshes automatically according to the setting entered here (in seconds).
This attribute is only displayed when the user is logged on as System Administrator.
Wireless Link Status
As the attribute name suggests it displays the current status of the wireless link. A state of
‘Up’ on a green background indicates that a point-to-point link is established. A state of ‘Down’
on a red background indicates that the wireless link is not established.
Maximum Transmit Power
The maximum transmit power that the local wireless unit is permitted to use to sustain a link.
Remote Maximum Transmit Power
The maximum transmit power that the remote wireless unit is permitted to use to sustain a
link.
93
Transmit Power
Transmit power histogram is expressed in dBm and presented as: max, mean, min, and
latest. The max, min and latest are true instantaneous measurements; the mean is the mean
of a set of one second means. See Section 7.3.1 Histogram Data.
Receive Power
Receive power histogram is expressed in dBm and presented as: max, mean, min, and latest.
The max, min and latest are true instantaneous measurements; the mean is the mean of a set
of one second means. See Section 7.3.1 Histogram Data.
Vector Error
The vector error measurement compares the received signal’s In phase / Quadrature (IQ)
modulation characteristics to an ideal signal to determine the composite error vector
magnitude. The results are stored in an histogram and expressed in dB and presented as:
max, mean, min and latest. The max, min and latest are true instantaneous measurements;
the mean is the mean of a set of one second means. The expected range for Vector Error
would be approximately -2dB (NLOS link operating at sensitivity limit on BPSK 0.67) to –33dB
(short LOS link running 256 QAM 0.83). See Section 7.3.1 Histogram Data.
Link Loss
The link loss is the total attenuation of the wireless signal between the two point-to-point units.
See Section 7.3.1 Histogram Data.
The link loss calculation presented below:
Equation 3 - Link Loss
Pll = PTx − PRx + g Tx + g Rx

Where is
Pll Link Loss (dB)
PTx Transmit power of the remote wireless unit

(dBm)
PRx Received signal power at the local unit

(dBm)
Antenna gain at the remote and local units
respectively (dBi). The antenna gain of the
gTx , g Rx PTP 600 Series bridge (23.5 dBi) is used
unless one or both of the units is a
Connectorized version.
Transmit Data Rate

The data rate in the transmit direction, expressed in Mbps and presented as: max, mean, min,
and latest in an histogram format. The max, min and latest are true instantaneous
measurements; the mean is the mean of a set of one second means. See Section 7.3.1
Histogram Data. Expected data rates can be found in Section 13 Data Rate Calculations.
Receive Data Rate
The data rate in the receive direction, expressed in Mbps and presented as: max, mean, min,
94
Link Capacity
The maximum aggregate data rate capacity available for user traffic, assuming the units have
been connected using Gigabit Ethernet. The link capacity is variable and depends of the
prevailing wireless conditions as well as the distance (range) between the two wireless units..
Transmit Modulation Mode
The modulation mode currently being used on the transmit channel. A list of all the modulation
modes can be found in Section 13 Data Rate Calculations, where data rate calculations plots
are given for each available modulation mode.
Receive Modulation Mode
The modulation mode currently being used on the receive channel. A list of all the modulation
modes can be found in Section 13 Data Rate Calculations, where data rate calculations plots
are given for each available modulation mode.
Link Symmetry
Link Symmetry: A ratio that expresses the division between transmit and receive time in the
TDD frame. The first number in the ratio represents the time allowed for the transmit direction
and the second number represents the time allowed for the receive direction.
NOTE
Link Symmetry is configured at the master ODU only. The appropriate matching Link
Symmetry is set at the slave ODU automatically. For example, if Link Symmetry is
configured as “2 to 1” at the master ODU, then the slave ODU will be set automatically
as “1 to 2”. In this example, the master-slave direction has double the capacity of the
slave-master direction.
Receive Modulation Mode Detail
This supplies the user with information regarding the receive modulation mode in use.
Possible values are:
• “Running at maximum receive mode”
• “Running at user-configured Max Modulation Mode”
• “Restricted due to byte errors on the wireless link or local Ethernet Tx Fifo Drops”
• “Restricted because a DFS channel change is in progress”
• “Restricted due to telecoms acquisition mode”
• “Restricted due to the low Ethernet link speed”
• “Limited by the wireless conditions”
Range
The range between the PTP 600 Series bridge ODUs. The PTP 600 Series Bridge displays
range in km by default, but if the user would prefer to display range using Miles, the ‘Distance
Units’ attribute should be set to imperial, as described in Section 7.14 Properties.
95
7.3.1 Histogram Data
The histogram is calculated over a one hour period. If the equipment has been running for
less than one hour, then the histogram is calculated over the current elapsed time. The data
used to compute the histogram statistics can be downloaded in an ASCII comma separated
value (CSV) format via the diagnostics CSV Download page, see Section 7.11.2 CSV
Download.
96
7.4 System Administration

Figure 50 shows the system administration login page. By default a system administrator
password is not set. Click the Login button to access the system administration features.
Figure 50 - System Administration Login Page
Once the password has been set using the ‘Change Password’ menu item, the system
administration pages will only be available after the user has entered the correct password.
The menu options that are available to the system administrator are:
• Configuration
• Statistics
• Installation
• Software Upgrade
• Spectrum Management
• Remote management
• Diagnostics Plotter
• Change Password
• License Key
• Properties
• Reboot
97
7.5 Configuration
The configuration of the PTP 600 Series Bridge is organized into the following sections:
• System configuration
• LAN configuration
• QoS Configuration
• Telecoms Configuration
• Save and Restore
The general configuration allows modification of high level administrative (descriptive)

attributes and high level wireless configuration.
The LAN configuration sub menu allows the system administrator to modify the Ethernet and
IP configuration of the PTP 600 Series Bridge.
The telecoms submenu displays the current status of the telecoms interface and allows the
configuration of interface loopbacks.
The save and restore submenu allows the system administrator to backup and restore the
bridge configuration. It is recommended after a unit has been successfully installed; a copy of
the active configuration is taken and archived by the system administrator.
7.5.1 System Configuration
The system configuration page (Figure 51) is used by the system administrator to configure
the PTP 600 Series Bridge’s high level administrative (descriptive) attributes and high level
wireless configuration.
98
Figure 51 - System Configuration Page
While the majority of the system configuration is entered during installation and should never
require changing, this page offers the system administrator the ability to change the basic
system parameters for both the wireless and Ethernet components.
Link Name
User defined identity for the unit (max 63 characters).
Link Location
Can be used as a generic scratch pad to describe the location of the equipment.
Master Slave Mode and Link Mode Optimization
Current settings are displayed and can be modified using the Installation pages, see Section
7.7 Installation.
Max Receive Modulation Mode
This is the maximum mode the unit will use as its adaptive modulation. By default the Max
Receive Modulation Mode is the highest mode available.
For minimum error rates, set the maximum modulation mode to the minimum necessary to
carry the required traffic.
Ethernet Capped Max Wireless Speed
When enabled this option will cap the wireless speed to a mode that the connected Ethernet
connection can sustain.
Maximum Transmit Power
This specifies the maximum transmit power in dBm of the system. It is country dependent and
although the user can change this in 1dB steps, it will be limited to that country’s regulations.
99
NOTE
UK requirement: In the UK there is a legal requirement to provide a minimum of 19
dB of transmit power control range. When the equipment is operating with a UK
License Key, an additional facility is provided on the configuration page that allows the
transmitted power to be reduced by 19 dB compared to the maximum allowed with a
simple single step control..
NOTE
Why Reduce Transmit Power? If the link losses are low and the link data rate and
availability targets are being easily achieved, the transmitted power level may be
reduced with a consequent benefit to other users of the band, such as fixed satellite
links.
7.5.2 QoS Configuration Page
The QoS configuration page (Figure 52) allows the system administrator to configure the
classification of priority encoded Ethernet frames into up to eight traffic classes.
Figure 52 - QoS Configuration Page
Priority Queue Mapping

Specifies the VLAN priority flag to packet queue mapping. The higher the queue number the
greater its priority.
100
7.5.2.1 Quality of Service Default Settings
The default classification rules are as shown in Table 9.
Table 9 – QoS Default Settings

Link Layer Priority Traffic Class
0 Q0
1 Q1
2 Q1
3 Q1
4 Q1
5 Q1
6 Q1
7 Q1
Untagged Q0
In the case where the ODU is upgraded from an earlier release that supports only two traffic
classes, the classification rules will be determined by the stored value of "VLAN High Priority
Traffic Threshold". For example, if the existing threshold was set to "VLAN User Priority 4 and
Above" then the classification rules would be initialized as shown in Table 10.
Table 10 – Classification rules upgrade example

0 Q0
1 Q0
2 Q0
3 Q0
4 Q1
5 Q1
6 Q1
7 Q1
Untagged Q0
101
The user interface also allows configuration of IEEE802.1Q classification rules as shown in
Table 11 using the button ‘Set Default 802.1Q Priority Mappings’.
Table 11 – IEEE802.1Q Classification rules

0 Q1
1 Q0
2 Q2
3 Q3
4 Q4
5 Q5
6 Q6
7 Q7
Untagged Q1
102
7.5.3 LAN Configuration
The LAN configuration page (Figure 53) is used by the system administrator to configure the
PTP 600 Series Bridge’s LAN interface.
Figure 53 - LAN Configuration Page
All of the LAN Configuration attributes are non-volatile, so once set, they will be used by the
unit even after a power on reboot. The LAN Configuration page contains the following fields:
IP Address
Internet protocol (IP) address. This address is used by the family of Internet protocols to
uniquely identify this unit on a network.
Subnet Mask
A subnet allows the flow of network traffic between hosts to be segregated based on a
network configuration.
Gateway IP Address
The IP address of a computer / router on the current network that acts as a gateway.
103
Use VLAN For Management Interfaces

This controls use of VLAN tags at the management interfaces (WWW/SNMP/SMTP/SNTP).
See Section 7.5.3.2 LAN Configuration Page for VLAN.
Ethernet Auto Negotiation
This enables the Ethernet configuration to be forced rather than auto negotiated.
CAUTION
The IEEE802.3 specification recommends enabling Auto Negotiation. The
configuration should only be forced if you are having problems with auto negotiation.
You must ensure that you configure both this unit and the Ethernet port to which it is
connected identically. If you force a fixed Ethernet Configuration on the PTP 600
Series bridge then you MUST also force the same fixed configuration on the
equipment to which it is connected. If you fail to force the configuration of the
connected equipment, its automatic configuration mechanisms will normally cause a
duplex mismatch, and you will receive greatly reduced throughput!
When Ethernet Auto Negotiation is Disabled the format of the LAN configuration page
changes see Section 7.5.3.3 LAN Configuration Page – Manual Ethernet Configuration.
Auto Neg Advertisement
This controls the rates that the auto negotiation mechanism will advertise as available.
CAUTION
Over the air throughput will be capped to the rate of the Ethernet interface at the
receiving end of the link.
Ethernet Auto Mdix
This enables/disables the Auto Medium Dependent Interface (MDI)/Medium Dependent
Interface Crossover (MDIX) capability. Default is “Enabled”.
Drop Ethernet Link On Wireless Link Down
When this option is enabled the Ethernet link is momentarily dropped when the wireless link
goes down. This feature is used to indicate to the connected network equipment that this
Ethernet link is no longer available, thus causing STP (Spanning Tree Protocol) to re-route
packets through an alternative link.
Local Packet Filtering
When Local Packet Filtering is “Enabled”, the bridge learns the source MAC addresses of
devices transmitting Ethernet packets on the local Ethernet network, and only bridges packets
to the remote unit if the destination MAC address has not been learned as a 'local' device.
When Local Packet Filtering is ‘Disabled’ the bridge does not learn the source MAC
addresses of devices transmitting Ethernet packets on the local Ethernet network, and
bridges ALL Ethernet packets received to the remote unit. Local Packet Filtering should be
disabled when external Ethernet switching hardware or a router is present. The default setting
for Local Packet Filtering is disabled.
7.5.3.1 Reboot Verification
A number of attributes, such as IP Address, Subnet Mask and Gateway IP Address and
VLAN settings will require a reboot before they are used. If any of these attributes are
changed a reboot screen appears asking the user to verify the reboot (Figure 54 or Figure
55).
104
Figure 54 - Configuration Reboot Page
Figure 55 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled
This will be followed by a pop-up dialogue box asking to confirm the action.
NOTE
At this point you will lose connection to the unit. If you have just changed the IP
Address, you now have to reconnect to the unit using the address just set.
7.5.3.2 LAN Configuration Page for VLAN
The layout of the LAN Configuration page changes if this attribute is enabled in order to allow
the VLAN VID and VLAN Priority to be set, see Figure 56. The VLAN settings are applied only
after the unit is rebooted.
CAUTION
You must ensure that you can access the VLAN which you configure here, otherwise
you will be unable to access the unit following the next reboot.
The PTP 600 management function is only compatible with single VLAN tagged
packets. Any management packet with two or more packets will be ignored.
105
Figure 56 - VLAN Configuration Fields
When VLAN is enabled, the LAN Configuration page contains the following extra fields:
Use VLAN For Management Interfaces

This control can be configured with one of the following three values:
No VLAN Tagging
IEEE 802.1Q Tagged (C-Tag, Type 8100)
IEEE 802.1ad Tagged (S-Tag or B-Tag, Type 88a8)
VLAN Management VID
This 802.1Q or 802.1ad VLAN ID (VID) will be included in packets generated by the
management interfaces. Valid settings are in the range 0 to 4094.
VLAN Management Priority
This 802.1Q or 802.1ad VLAN Priority will be included in packets generated by the
management interfaces. Valid settings are in the range 0 to 7.
VLAN Management VID Validation
If enabled, the management interfaces will only respond to Ethernet packets tagged with the
configured Management VID; otherwise packets with any VID will be accepted.
106
7.5.3.3 LAN Configuration Page for Manual Ethernet Configuration
The layout of the LAN Configuration page changes if Ethernet Auto Negotiation is Disabled,
see Figure 57.
Figure 57 - LAN Configuration Page - Manual Ethernet Configuration
When Ethernet Auto Negotiation is Disabled, the LAN Configuration page contains the
following extra field:
Force Configuration
This option allows the user to force the speed and duplex setting of the Ethernet interface.
Over the air throughput will be capped to the rate of the Ethernet interface at the receiving
end of the link.
NOTE
Instead of forcing configuration, the IEEE802.3 specification recommends enabling
Auto Negotiation with only the specific ability or abilities advertised.
7.5.4 Save and Restore
The save and restore feature of a PTP 600 Series Bridge allows the system administrator to
backup the operation configuration of the wireless unit. It is recommended that this facility is
used immediately after a successful PTP 600 Series Bridge installation or prior to any
software upgrade. In the unlikely event that a unit has to be replaced in the field, the
replacement unit can be reconfigured by simply playing back the saved configuration file.
107
7.5.4.1 Save Configuration File
To save the configuration file click on the ‘Save Configuration File’ button (Figure 58) and
save the configuration file (.cfg) to the hard drive of your computer.
Figure 58 - Save and Restore Configuration Page
The configuration file format is MAC-mm-mm-mm_IP-iii-iii-iii-iii.cfg, where mm and iii are

the lower 3 bytes of the MAC address and the unit IP address respectively.
NOTE
There is a feature of Internet Explorer (all versions) that looks at the content of any
downloadable file and decides whether to treat the file as ASCII or binary. As a result
of this feature, Internet Explorer always treats the configuration file as ASCII and
attempts to display it instead of downloading it. Firefox (all versions) makes no such
assumption.
108
Figure 59 - Save Configuration File Screen
The configuration file is encoded using an ASCII encoding scheme. An example is show in
Figure 60.
1
Figure 60 – PTP 600 Example Configuration File
109
CAUTION
The configuration file is currently restricted to a single software version and can only
be restored into a wireless unit operating the software version indicated in the
configuration file header.
7.5.4.2 Restore Configuration File
The configuration file can also be used when swapping out a faulty wireless unit. If one of the
wireless units is replaced on a wireless link a configuration file captured from the faulty unit
can be uploaded into the new unit to speed up replacement.
NOTE
The license key of the faulty unit should be setup on the replacement unit before the
configuration file is loaded. This can be obtained either from the Quick Start Guide
supplied with the faulty wireless unit or directly from Motorola. The target MAC
address at the other end needs to be changed to ensure that it is using the MAC
address of the replaced unit.
The restoration of configuration files can be performed using the Restore configuration tool.
Using the browser button to locate the configuration file you wish to restore then click the
‘Restore Configuration File and Reboot’ button (Figure 61). The user will then be prompted to
confirm the action (Figure 62).
Figure 61 - Restore Configuration File Pop Up Screen
110
Figure 62 - Reset Configuration and Reboot Confirmation Pop-up
On confirmation the PTP 600 Series Bridge will:

• Upload the configuration file
• Perform data integrity checking
• Erase previous configuration
• Apply the new configuration
• Restart
After the unit has restarted the entire configuration from the configuration file will now be
active. The IP address of the unit may have also been changed. The user can check the new
IP address by reading the header of the configuration file, Figure 60.
CAUTION
A reboot is always required to restore a configuration file.
111
7.5.5 Telecoms Configuration
The Telecoms page (Figure 63) is available when the Telecoms Interface has been set to
either T1 or E1 in the Installation process.
The unit displays the interface setting and line code for the available telecoms channels. The
PTP 600 Series Bridge is able to support two T1 or E1 channels. These channels are referred
to as "Channel A" and "Channel B".
The "Channel B" configuration and controls will be displayed only when the second channel is
enabled.
Figure 63 - Telecoms Data Entry
The Telecoms page contains the following fields:
Telecoms Interface
May be either T1 or E1, reflecting the Installation setting.
Line Code
Displays the Line Code setting for each channel. The Line Code configuration must match the
configuration of the connected equipment and may be set using the Installation process.
Cable Length
The Cable Length setting is applicable in T1 mode only and shows the cable length specified
in the installation process.
112
Loopback
Allows the T1 or E1 data stream to be looped back at the copper or wireless interface. During
normal operation the loopback must be set to "None". It may be helpful during installation to
test the telecoms links by performing loopback connections.
A "Copper" loopback connects the received data on a given telecoms interface to the transmit
interface. A "Copper" loopback may be used, in conjunction with a Bit Error Rate Tester, to
confirm that the correct connections have been made to the ODU. This mode cannot be used
for resistance tests as it is only capable of looping back valid telecoms signals.
A "Wireless" loopback sends the telecoms data received across the wireless link back across
the link on the same Telecom channel. The link may be checked using, for example, a Bit
Error Rate Tester to ensure that no errors are detected.
A typical T1 or E1 installation might include a "Copper" loopback on the local unit followed by
a "Wireless" loopback on the remote unit.
It is important to remove all loopbacks on channels for normal operation. Alarms on the
Home Page indicate the presence of loopbacks on either channel.
Lowest Telecoms Modulation Mode

The user defined lowest modulation mode at which telecoms data can be sent. If the link
cannot sustain telecoms data in this mode then the effective lowest modulation mode may
differ
Lowest Dual Payload Modulation Mode; Lowest Single Payload Modulation Mode
Indicate the effective lowest modulation mode at which telecoms data can be sent, subject to
wireless capacity and latency limitations. Under some circumstances, these settings may
differ from the user defined Lowest Telecoms Modulation Mode described above.
113
7.6 Statistics
The System Statistics page (Figure 64) displays some key statistics of the Ethernet Bridge
and the underlying wireless performance.
The numbers in brackets display the number of packets received since the last page refresh.
Figure 64 - System Statistics Page
The System Statistics page contains the following fields:
Wireless Tx Packets
This displays the total number of good packets the bridge has sent for transmission by the
wireless interface.
114
Wireless Rx Packets
This displays the total number of good packets the bridge has received from the wireless
interface.
Ethernet Tx Packets
This displays the total number of good packets the bridge has sent for transmission by the
local Ethernet interface.
Ethernet Rx Packets
This displays the total number of good packets the bridge has received from the local
Ethernet interface.
Packets To Internal Stack
This displays the total number of good packets the bridge has transmitted to the internal stack
(for example, ARP requests, PING requests, HTTP requests).
Packets From Internal Stack
This displays the total number of good packets the bridge has received from the internal stack
(for example ARP responses, PING replies, HTTP responses).
Link Symmetry
Link Symmetry: A ratio that expresses the division between transmit and receive time in the
TDD frame. The first number in the ratio represents the time allowed for the transmit direction
and the second number represents the time allowed for the receive direction.
Transmit Data Rate
The data rate in the transmit direction, expressed in Mbps and presented as: max, mean, min,
Receive Data Rate
The data rate in the receive direction, expressed in Mbps and presented as: max, mean, min,
Aggregate Data Rate
The sum of the data rate in the directions expressed in Mbps and presented as: max, mean,
min, and latest in an histogram format. The max, min and latest are true instantaneous
Link Capacity
The maximum aggregate data capacity available for user traffic under the current radio link
conditions, assuming the units have been connected using Gigabit Ethernet. The sum of the
displayed Transmit and Receive data rates may be lower than this figure if the link isn't fully
loaded by the current traffic profile.
Transmit Modulation Mode
The modulation mode currently being used on the transmit channel. The number in brackets
after the modulation mode and coding rate string is the effective data rate available to all MAC
layer protocols. List of all the modulation modes can be found in Section 13 Data Rate
Calculations, where data rate calculations plots are given for each available modulation mode.
115
Receive Modulation Mode

The modulation mode currently being used on the receive channel. The number in brackets
after the modulation mode and coding rate string is the effective data rate available to all MAC
layer protocols. List of all the modulation modes can be found in Section 13 Data Rate
Calculations, where data rate calculations plots are given for each available modulation mode.
Receive Modulation Mode Detail
This supplies the user with information regarding the receive modulation mode in use.
Possible values are:
• “Running at maximum receive mode”
• “Running at user-configured Target Modulation Mode”
• “Restricted because Installation is armed”
• “Restricted because of byte errors on the wireless link”
• “Restricted because a DFS channel change is in progress”
• “Restricted due to the low Ethernet link speed”
• “Limited by the radio conditions”
Signal Strength Ratio

The Signal Strength Ratio is the ratio of the power received by the Vertical / Horizontal
receivers and presented as: max, mean, min, and latest in an histogram format. The max, min
and latest are true instantaneous measurements; the mean is the mean of a set of one
second means. See Section 7.3.1 Histogram Data.
Wireless Link Availability
Expresses the link availability as a percentage of time since the first successful registration
after a system restart, expressed as a percentage to four decimal places.
Byte Error Ratio
The ratio of detected Byte errors to the total number of bytes since the last system reboot.
This is a true measure of link quality as this measurement is made continually using null
frames when there is no user data to transport.
Statistics Page Refresh Period
The statistics page refreshes automatically according to the setting entered here (in seconds).
Reset System Counters
By pressing this button all counters in the system are reset to zero.
Reset System Histograms
All histograms are reset, and the calculation period is restarted.
116
7.6.1 Detailed Counters
The Detailed Counters page (Figure 65) displays detailed statistics of the Ethernet Bridge and
the underlying wireless performance.
Figure 65 - Detailed Counters Page
117
The Detailed Counters page is subdivided into two columns. Column one presents the
detailed statistics for the bridge’s Ethernet interface. Column two relates to the wireless
interface.
The Counters have the following definitions:
Tx & Rx Octets
Total number of octets (bytes) transmitted or received over the interface.
Rx Drops
Total number of frames dropped due to the lack of sufficient capacity in the receive buffer.
Rx Packets
Total number of packets received by the interface. This includes both good and bad packets.
Rx Broadcasts
Total number of good broadcast packets.
Rx Multicasts
Total number of good multicast packets.
Rx CRC and Align
Total number of packets with CRC or frame alignment errors.
Rx Undersize
Total number of packets received that are less than 64 bytes and have a valid CRC.
Rx Oversize
Total number of packets received that are greater than the maximum number of bytes with a
valid CRC.
Rx Fragments
Total number of packets that are less than 64 bytes with an invalid CRC (these packet types
are also known as runts).
Rx Jabbers
Total number of packets received that are greater than the maximum number of bytes with an
invalid CRC.
Rx 64 Bytes
Total number 64 byte frames received
Rx 65 to 127 Bytes
Total number of frames received in the size range 65 to 127 bytes.
Rx 128 to 255 Bytes
Rx 256 to 511 Bytes
Rx 512 to 1023 Bytes
118
Rx 1024 to Max
Total number of frames received in the size range 1024 to Maximum bytes.
Tx Drops
Total number of frames dropped due excessive collisions, late collision and frame ageing.
Tx Packets
Total number of packets received by the interface. This includes both good and bad packets.
Tx Broadcasts
Total number of good broadcast packets.
Tx Multicasts
Total number of good multicast packets.
Tx Collisions
Total number frames experiencing collisions.
Tx 64 Bytes
Total number 64 byte frames transmitted
Tx 65 to 127 Bytes
Total number frames transmitted in the size range 65 to 127 bytes.
Tx 128 to 255 Bytes
Tx 256 to 511 Bytes
Tx 512 to 1023 Bytes
Tx 1024 to Max
Total number frames transmitted in the size range 1024 to Maximum bytes.
Tx FIFO Drops
Total number frames dropped due to lack of capacity in the transmit buffer, for example when
the PTP 600 Series bridge is connected to the local Ethernet at a connection speed of less
than 1 Gbps.
Rx & Tx Frames Q0…Q7
Total number of received or transmitted frames for each Traffic Class (Q0 to Q7).
Rx & Tx Pause Frames
Total number of received or transmitted pause frames (Ethernet interface only).
Packets To Internal Stack
The total number of good packets the bridge has transmitted to the internal stack.
Packets From Internal Stack
The total number of good packets the bridge has received from the internal stack
Packets Ignored By Internal Stack
The total number of bad packets the bridge has transmitted to the internal stack.
Rx Classifier Drops
Total number of received frames dropped due to the application of classifier rules.
119
Detailed Counters Page Refresh Period

The statistics page refreshes automatically according to the setting entered here (in seconds).
7.7 Installation
There follows a description of the installation pages along with their use during the installation
configuration process. The actual installation process is described in Section 7.7.2 Manual
Configuration”.
NOTE
This section assumes that the integrated PTP 600 is being installed. If the
connectorized variant is being installed, refer to Section 10.2 Software/Features for
details of the additional functionality that must be configured.
7.7.1 Factory Configuration
All wireless links are shipped as paired units. They are pre-configured at the factory so that
they can be installed without the user supplying any configuration. Each wireless link is
shipped with a deployment guide. Attached to the deployment guide is a summary of the pre-
configured configuration data. Table 12 shows a sample link configuration. The values in red
type have been committed to the wireless unit’s non-volatile storage.
Table 12 – 600 Series Bridge Factory Configuration Values
Example PTP 600 Series Configuration Data
For your convenience these two units have been pre-configured as a link
Units:
ODU serial number ODU serial number
016780000FFF 016780000FC7
Ethernet MAC address Ethernet MAC address
00:04:56:80:0F:FF 00:04:56:80:0F:C7
Configured as:
120
Master Slave
Target MAC address Target MAC address
00:04:56:80:0F:C7 00:04:56:80:0F:FF
License Key License Key
A471-FE88-428D-E1F3 534F-4F54-D1B0-E2DA
IP Address IP Address
169.254.1.2 169.254.1.1
CAUTION
The factory default configuration is limited in range to 40 Km (25 miles). If you wish to
install a wireless link with a range of > 40 Km (> 25 miles) and < 200 Km (< 124
miles) or < 5 Km (< 3 miles) you must follow the Section 7.7.2 Manually Configuring
The Wireless Units.
CAUTION
The factory default configuration is set to Region 1. Region 1 allows the PTP 600
Series bridge a maximum transmit power of 25 dBm. If the local regulatory regime
limits the maximum transmit power (EIRP) to less than 25 dBm, you should obtain a
new license key containing the correct region code from your local distributor or direct
from Motorola. Alternatively in the short term, you should reduce the maximum
transmit power by following the procedures in Section 7.7.2 Manually Configuring The
Wireless Units.
7.7.2 Manual Configuration
If the installer / system administrator wishes, they may modify the default installation
configuration. If only the IP addresses (network configuration) are incorrect it is recommended
that the values are changed via the configuration menu (Section 7.5.3 LAN Configuration).
NOTE
If any other parameters (for example Region Code) require modification, then it is
recommended that the system administrator use the Installation process.
121
The PTP 600 Series bridge operational software requires a license key (Figure 66) to enable
the wireless bridging capability and programs region code specific parameters in to the unit.
Figure 66 - License Key Data Entry
A license key is programmed into each unit during production and can be found written on the
Configuration Data Summary Label which is attached to the Quick Install Guide. If
subsequently the license key has been mislaid, replacement keys can be applied for online or
via your distributor.
If a valid license key is not detected in the unit’s non-volatile memory then the user is
prompted to enter a valid key. It should be noted that 600 Series bridge units are shipped as
link pairs and, as such, valid license keys are entered during the production process. To enter
a license key simply type or paste the license key into the data entry box (Figure 66) and click
the ‘validate license key’ button.
122
7.7.3 Current Installation Summary

When Installation is selected from the menu navigation bar, the Current Installation
Summary page is displayed (Figure 67). Review the current configuration attributes. If any
attributes require changing, select Continue to Installation Wizard.
Figure 67 – Current Installation Summary
123
7.7.4 Installation Step 1 - Interface Configuration
Step 1 of the installation process requires the installer to enter the Internet Protocol (IP)
configuration, VLAN configuration and the telecoms interface (Figure 68).
Figure 68 - Installation Interface Configuration
The Interface Configuration page contains the following fields:
IP Address
Internet protocol (IP) address. This address is used by the family of Internet protocols to
uniquely identify this unit on a network.
Subnet Mask
A subnet allows the flow of network traffic between hosts to be segregated based on a
network configuration. By organizing hosts into logical groups, a subnet can improve network
security and performance.
Gateway IP Address
The IP address of a computer / router on the current network that acts as a gateway. A
gateway acts as an entrance / exit to packets from / to other networks.
Use VLAN Management Interface
Controls whether the management interfaces (HTTP/SNMP/SMTP/SNTP) use a VLAN.
Selecting this option presents the user with extra fields in which to enter the Management
VLAN ID, Priority and whether to validate the VLAN ID. If the user modifies this control, a
warning dialog is displayed see Figure 69.
124
Telecoms Interface
This allows the activation of the PTP 600 Series bridge telecoms interface. The selection
options are None, E1 or T1. Mixed T1/E1 configurations are not permitted.
Figure 69 - VLAN Warning
Once complete, click the ‘Submit Internet Protocol Configuration’ button or the ‘Next’ link.
125
7.7.4.1 Telecoms Interface
If the telecoms interface is configured to either T1 or E1 then Step 1 of the installation

process contains additional configuration fields (Figure 70).
Figure 70 - Telecoms Configuration Interface
The additional E1 or T1 fields are:
Telecoms Channel Selection

This allows the user to configure one or two interfaces (Channel A or Channel A and B).
Channel A Line Code
The line code setting of the telecoms interface. This must match the setting of the device
connected to this interface.
Channel B Line Code
The line code setting of the telecoms interface. This must match the setting of the device
connected to this interface.
126
NOTE
If a copper loopback is used to test the E1/T1 link, ensure that the test set is
configured manually. If the test set is allowed to configure automatically, neither it nor
the ODU send a signal until they receive one, so the test appears to fail.
Channel A/B Cable Length

This field is applicable to the T1 operating mode only. It configures the T1 transceiver to
output a signal suitable for driving a cable of the specified length. This should be set to reflect
the length of cable between the wireless unit and the connected equipment.
Lowest Telecoms Modulation Mode
The lowest modulation mode at which telecoms data will be sent, if there is sufficient link
capacity.
In conjunction with the LINKPlanner tool, this setting may be used to optimize the latency for
links which operate in consistently high modulation modes. High data rate links are able to
support lower latencies.
The lowest telecoms modulation mode is selected from a rate ordered drop-down list. If this
selected mode has insufficient capacity to support the telecoms data then the effective lowest
modulation mode, determined when the wireless link starts, will be higher. The effective
lowest modulation mode is displayed on the Telecoms Configuration page.
127
7.7.5 Installation Step 2 - Wireless Configuration
Step 2 of the installation process requires the installer to enter the wireless configuration
parameters. Figure 71 is an example of the Wireless Configuration screen.
Figure 71 –Wireless Configuration
128
The contents of the Wireless Configuration screen vary as follows:

• PTP 25600: Frequency Band field is also displayed.
• Channel Bandwidth options vary depending upon frequency variant and region. For more
information, see Table 4.
• PTP 49600: Lower Center Frequency is not displayed.
Screen contents also vary depending upon the options selected as follows:
• If Spectrum Management Control is set to “Fixed Frequency”, the Lower Center
Frequency field is replaced by Fixed Tx Frequency and Fixed Rx Frequency.
• If Platform Variant is set to “Connectorized”, Antenna Gain and Cable Loss are also
displayed. For more information about the configuration of connectorized PTP 600 units,
refer to Section 10.2 Software/Features.
The Wireless Configuration page contains the following fields:
Target MAC Address

This is the MAC Address of the peer unit that will be at the other end of the wireless link. This
is used by the system to ensure the unit establishes a wireless link to the correct peer. The
MAC Address can be found embedded within the serial number of the unit. The last six
characters of the serial number are the last three bytes of the unit’s MAC address.
NOTE
A PTP 600 Series system is shipped as a pair of units with pre-loaded correct MAC
addresses. Target MAC addresses will only need to be entered if an existing unit has
to be replaced in the field or the units configuration has been erased.
Master Slave Mode

At this point it is necessary to decide which end will designate a Master. The Master unit is the
controlling unit with respect to the point-to-point link and its maintenance. The master
transmits until the link is made, while the Slave listens for its peer and only transmits when the
peer has been identified.
Link Mode Optimization
Optimizes the link behavior according to the type of traffic that will be bridged. There are two
modes to choose from: IP and TDM. For more information, see Section 3.9 Link Mode
Optimization.
TDD Synchronization Mode
Enables the TDD Synchronization feature (see Section 3.8 Time Division Duplex (TDD)
Synchronization for basic description and Section 11 TDD Synchronization Installation and
Configuration for installation and configuration details).
Tx Max Power
This attribute controls the maximum transmit power the unit is permitted to use when installing
and executing the wireless link. The maximum setting for a particular region or country is
controlled by the License Key.
129
Ranging Mode
During installation, the wireless units perform “Automatic Ranging”. The ranging mode allows
the installer to control the behavior of the system’s automatic ranging algorithms. The default
value is 0 to 40 km (0 to 25 miles). If the installer is required to install a link of greater than 40
km (25 miles) then the ranging mode attribute MUST be configured to ‘0 to 100km’ (0 to 62
miles) or ‘0 to 200km’ (0 to 124 miles) mode depending on the range of the link.
NOTE
If preferred, PTP 600 Series Bridge range functions can be configured to operate in
miles, as described in Section 7.14 Properties.
Target Range
Installers that know the range between the two wireless units to within ± 1 km can use the
target range mode. The main advantage of the target range mode is that it reduces the time
taken by the units to range. To use the target range mode the installer MUST select Target
Range as the ranging mode and enter the approximate range in km in the Target range data
entry field at both ends of the link.
Platform Variant
Chooses between an integrated unit or a connectorized unit that requires an external
antenna.
Frequency Band
Only displayed for the PTP 25600 frequency variant, which operates in one of three bands as
described in Section 4.4 Variable Channel Bandwidth Operation:
• Lower: 2496 MHz to 2568 MHz
• Middle: 2572 MHz to 2614 MHz
• Upper: 2624 MHz to 2690 MHz
Channel Bandwidth
Users can choose a variable channel bandwidth for the available spectrum. The selection
depends upon the frequency variant and region. For more information, see Table 4.
Link Symmetry
(Master only) Values of "Adaptive", "2 to 1", "1 to 1" and "1 to 2" can be selected. The
adaptive setting allows link symmetry to vary dynamically in response to offered traffic load.
The remaining values select three options for fixed division between transmit and receive time
in the TDD frame of the master ODU. The first number in the ratio represents the time allowed
for the transmit direction and the second number represents the time allowed for the receive
direction.
The appropriate matching Link Symmetry is set at the slave ODU automatically. For example,
if Link Symmetry is configured as “2 to 1” at the master ODU, then the slave ODU will be set
automatically as “1 to 2”. In this example, the master-slave direction has double the capacity
of the slave-master direction.
NOTE
Link Symmetry is subject to the following restrictions:
"Adaptive" is not supported in regions where radar avoidance is in use.
"Adaptive" is not supported when link optimization is set to "TDM".
"Adaptive" is not supported in 5 MHz channel bandwidth.
"2 to 1" and "1 to 2" are not supported in 5 MHz channel bandwidth.
“2 to 1” and “1 to 2” are not supported when E1/T1 services are enabled.
130
Spectrum Management Control

Is used to configure the PTP 600 Series Bridge’s Spectrum Management features, see
Section 7.9 Spectrum Management for more details. In regions that do not mandate DFS
(Radar Detection), the Spectrum Management Control options are “i-DFS” and “Fixed
Frequency”. In regions that mandate DFS (Radar Detection), the Spectrum Management
Control options are “DFS” and “DFS with i-DFS”.
The Spectrum Management Control is disabled if the regulatory requirement is fixed
frequency only (for example if the frequency variant is PTP 25600).
Lower Center Frequency
Not displayed for the PTP 49600. Not displayed when Spectrum Management Control is set
to “Fixed Frequency”. The software for the PTP 600 Series Bridge allows a user to optionally
adjust the channel center frequencies. Changing the Lower Center Frequency attribute
causes all channel center frequencies to be offset. It effectively slides the channelization up or
down.
NOTE
Because the 4.9 GHz spectrum is restricted by license, the Lower Center Frequency
is fixed for the PTP 49600 and is therefore not displayed.
CAUTION
The lower center frequency attribute must be configured to the same value for both
the master and slave. Failure to do so will cause the wireless link to fail
reestablishment. The only way to recover from this situation is to modify the Lower
Center Frequency attribute so that they are identical on both the master and slave
unit.
Default Raster
If this is set to “On”, the list of options presented in the fixed Tx frequency box is limited by the
default raster.
Fixed Tx Frequency, Fixed Rx Frequency
Only displayed when Spectrum Management Control is set to “Fixed Frequency”. The
software for the PTP 600 Series Bridge allows a user to optionally fix the Transmit and the
Receive frequencies for a wireless link. The settings must be compatible at each end of the
link. Once configured, the spectrum management software will not attempt to move the
wireless link to a channel with lower co-channel or adjacent channel interference. Therefore
this mode of operation is only recommended for deployments where the installer has a good
understanding of the prevailing interference environment.
Figure 72 shows an example fixed frequency configuration for a 30 MHz channel bandwidth.
In this example, the Fixed Transmit Frequency is set to 5742 MHz and the Fixed Receive
Frequency is set to 5742 MHz. Care must be taken when configuring the Fixed Transmit and
Receive Frequencies to ensure that both frequencies are on the same channel raster as the
Lower Center Frequency. For example, if the channel raster is 10 MHz, both the Fixed
Transmit and Receive Frequencies must be a multiple of 10 MHz from the Lower Center
Frequency (5752 = 5742 + 10 MHz) and (5782 = 5742 + 10 MHz × 3).
NOTE
A raster limits the selection of the Rx frequency based upon the setting of the Tx
frequency.
131
Tx Color Code, Rx Color Code

The Tx Color Code and Rx Color Code attributes need only be considered when the unit is
installed in a dense network of synchronized PTP 600 units and where some of the PTP 600
units are operating on the same frequency. In this case, the value would normally be derived
by a network radio planner. In all other cases, it is strongly recommended that this attribute is
left at the default value of "A".
NOTE
The value of Tx Color Code MUST always match the value of Rx Color Code at
the other end of the link.
Installation Tones
Where the use of audio installation tones is not required, this control allows the installer to
optionally disable the tone generator during the installation process.
Figure 72 – Fixed Frequency Configuration Example
7.7.5.1 Submit Wireless Configuration
Once the installer is satisfied with the wireless configuration options then the Submit
Wireless Configuration button or the Next link should be clicked.
132
7.7.6 Installation Step 3 - Confirm Configuration
Step 3 of the installation process requires the installer to confirm the wireless configuration
parameters. Figure 73 is an example of the Confirm Configuration screen. The screen
contents vary depending upon the product variant and configuration options selected.
Figure 73 – Confirm Installation Configuration
133
If the settings are correct and appropriate, click the “Confirm Configuration, Arm Installation
and Reboot” button. The user will now be prompted to confirm the action (Figure 74).
Figure 74 - Reboot Confirmation Pop Up
All the attributes are committed to non-volatile memory. Immediately following the write to
non-volatile memory the unit is reset.
NOTE
If you have changed the Ethernet parameters you must reconnect using the correct
network and address settings.
134
7.7.7 Disarm Installation
Figure 75 is an example of the Disarm Installation screen. The screen contents vary
depending upon the product variant and configuration options selected.
Figure 75 – Disarm Installation
135
When Section 7.7.6 Installation Step 3 - Confirm Configuration is complete, the installation is
armed and rebooted. Pressing the “Disarm Installation Agent” button completes the
installation process and the audible installation tone will be switched off. If the installer wishes
to modify the installation configuration then the ‘Back’ link can be used to access the
installation steps described above.
The installation process is completed when both ends of the link are ‘disarmed’.
After disarming the wireless link the user is presented with one of two possible configuration
pages, see Figure 76 and Figure 77. The screen presents hyperlinks to the main
configuration and spectrum management pages.
Figure 76 - Optional Post Disarm Configuration 1
Figure 77 - Optional Post Disarm Configuration 2
After installation the system administrator may wish to modify the wireless units descriptive
configuration (link name and link location). In addition the system administrator may wish to
change the spectrum management configuration of the wireless unit, or look at the analysis of
the 5.8 GHz spectrum to see if the automatic channel selection is appropriate for the system
administrator’s network. It is also recommended that a backup copy of the wireless units
configuration is taken. Hyperlinks are provided on the post disarm page for ease of use.
136
7.7.8 Graphical Install
To aid the installation of wireless links two graphical installation aids have been introduced in
this 600 Series system version.
• A PDA installation screen
• A larger installation screen available from the main HTTP management interface.
The design of the installation screen has been deliberately kept simple and uncluttered. An
example of the installation screen is shown in Figure 78. Both the PDA and the large format
installation screen have the same content and only differ in size. The PDA installation screen
is 232 by 220 pixels to be compatible with the typical size of a PDA screen.
Figure 78 – Graphical Installation Screen
The screen displays the receive power over the last three minutes. This will allow the installer
to slowly sweep the antenna during installation and monitor the variation in signal strength
with angular position. The screen automatically refreshes every three seconds.
The screen also displays the current state of the wireless link in two ways. First, the actual
state of the wireless link is written in the top left corner of the screen. The instantaneous
receive power bar also encodes the state of the wireless link using green to signify that the
wireless link is up and red for all other states.
137
For the more technically, aware the installation metric is simply the instantaneous receive
power in dBm + 100.
The PDA installation tool is accessed via a hidden URL http://<ip-address>/pda.cgi. It should
be noted that this link is only available after the user has logged in as system administrator.
The large screen version of the graphical user interface is available as a submenu option of
the installation process.
7.8 Software Upgrade

The PTP 600 Series system has two software image banks; one is a fixed image which is
stored in protected non-volatile memory and cannot be modified by the user. The second
bank is used by the system administrator to upgrade the firmware when necessary. Figure 79
shows the main software upgrade web page.
Figure 79 - Software Upgrade
The ‘Fixed’ or ‘Recovery’ image is used by the System Administrator to:

• Reset Ethernet configuration to default settings
• Erase Configuration
• Upgrade software
For a full description of the Recovery image see Section 8 Recovery Mode.
138
The software upgrade pages are used to update a unit’s operational software. The software
image to be uploaded should be downloaded to local storage from the Motorola web site. The
software image is delivered by Motorola as a compressed zip file. Once the zip file has been
downloaded, the user should extract the PTP 600 Series Software image, identifiable by its
‘.dld’ file extension.
7.8.1 Locate and Upload Software Image
The first step (Figure 79) is to use the “Browse” button to locate the software image
previously downloaded to local storage from the Motorola web site. Once the image is
located, the user should press the Upload Software Image button to start the software
upgrade process.
CAUTION
During the software upgrade process, ensure that the remote end is upgraded first
using the wireless connection, and then the local end can be upgraded.
The software image will now be uploaded to the unit. This upload should only take a few
seconds. Once complete the image is verified and validated to ensure that no errors occurred
during transfer and that the image is valid to run on the current platform. If there are any
problems a warning screen will appear.
The unit being upgraded will now display information about the build it currently has stored in
the image bank and the one that’s just been uploaded. If the image is not the right one, the
user has the option to go back and reload a new image. (See Figure 80).
139
Figure 80 - Software Upgrade Image Check
7.8.2 Program Software Image into Memory
The user should ensure that the correct image is shown before pressing the “Program
Software Image into Non-Volatile Memory” button. Once this button has been pressed the
image is stored into non-volatile memory, this process can take up to 60 seconds and must
not be interrupted.
CAUTION
If the upgrade process is interrupted during the erasure of the image bank, or during
the reprogramming of the image bank, the image bank will be left in a corrupt state. If
this occurs the software must be reloaded. All software images that are stored in non-
volatile memory are protected via the use of CRCs. If the software detects an invalid
CRC the image bank is marked as ‘corrupt’ and the PTP 600 Series bridge boot code
will boot the fixed software image. If this occurs the user must attempt to reload the
correct version of software.
During the write process the progress of the upgrade is displayed on the progress tracking
page (Figure 81). The upgrade process should not be interrupted. Interruption of this process
can result in a corrupt main software image, which will result in the recovery image been
booted at the next reset cycle.
140
Figure 81 - Software Download Progress Indicator
7.8.3 Software Upgrade Complete
When the software image has been written to non-volatile memory, Figure 82 is displayed
showing the status of the software upload.
Figure 82 - Software Upgrade Complete Page
7.8.4 Reboot After Software Upgrade
Reboot the unit by clicking the “Reboot Wireless Unit” button. You will be asked to confirm
this action as shown in Figure 83.
141
This will reboot the unit, taking up to 120 seconds. During this time you will not be able to
communicate with the unit.
If you cannot communicate with the unit after 120 seconds, this could indicate a problem with
the memory update process. Under these circumstances the user should enter “Recovery
Mode”, see Section 8 Recovery Mode.
After the reboot the user should check that the required software image is loaded and
running.
NOTE
Please ensure that you are upgrading the correct units. Units cannot be downgraded.
142
7.9 Spectrum Management

Spectrum Management Selection is the PTP 600 Series Bridge feature that monitors the
available wireless spectrum and directs both ends of the wireless link to operate on a channel
with a minimum level of co-channel and adjacent channel interference.
7.9.1 Wireless Channels
The PTP 600 Series Bridge operates using a set of predefined overlapping channels. There
are a different number of channels, depending on the raster mode selected. Each channel
occupies 30 MHz, 20 MHz, 15 MHz, 10 MHz or 5 MHz of wireless spectrum and is offset in
center frequency from its neighboring channel by 10 MHz or 6 MHz. It is important to note
that adjacent channels on the Spectrum management display have a 10 MHz or 6 MHz
overlap to the adjacent channel.
The default channelization can be modified by varying the lower center frequency attribute in
the installation process, as described in Section 7.7.5 Installation Step 2 - Wireless
Configuration.
7.9.2 Spectrum Management Measurements
The PTP 600 Series Bridge performs two mean signal measurements per TDD cycle, per
channel. This mean measurement represents the mean received signal power for the 40
microseconds measurement period.
The Spectrum Management algorithm collects measurements equally from all channels. This
process is called the Channel Availability Check (hereafter referred to by the acronym CAC).
The CAC uses a round-robin channel selection process to collect an equal amount of
measurements from each channel. It is important to note that the CAC measurement process
is not altered by the channel barring process. Measurements are still collected for all
channels irrespective of the number of barred channels.
7.9.3 Measurement Analysis
Spectrum Management uses statistical analysis to process the received peak and mean
measurement. The statistical analysis is based on a fixed, one minute, measurement
quantization period. Spectrum Management collects data for the specified quantization period
and only at the end of the period is the statistical analysis performed.
143
The analysis produces three key metrics for each channel:
Peak of Means
This is the largest mean interference measurement encountered during the quantization
period. The peak of means is similar to the peak of peaks and is useful for detecting slightly
longer duration spikes in the interference environment.
99.9% Percentile of the Means
This is the value of mean interference measurement which 99.9% of all mean measurements
fall below, during the quantization period. The 99.9% percentile metric is useful for detecting
short duration repetitive interference that by its very nature has a minimal effect of the mean
of means.
Mean of Means
This is the arithmetic mean of the measured means during a quantization period. The mean of
means is a coarse measure of signal interference and gives an indication of the average
interference level measured during the quantization period. The metric is not very good at
predicting intermittent interference and is included to show the spread between the mean of
means, the 99.9% percentile and the peak of means.
NOTE
The arithmetic mean is the true power mean and not the mean of the values
expressed in dBm.
Spectrum Management uses the 99.9% percentile as the prime interference
measurement. All subsequent references to interference level refer to this percentile
measurement.
The display of statistical measurement on the spectrum management page always shows a
statistical summary of all channel measurement. The statistical summary is controlled by the
Statistics Window attribute. This attribute defaults to a value of twenty minutes, which means
that the mean and percentile values displayed for each channel are calculated over the 20
minute period. All channel decisions are made using the values computed over the statistics
window period.
7.9.4 The Spectrum Management Master / Slave Relationship
The Spectrum Management operates in a master / slave relationship. The master is assumed
to be the link master configured during installation. All Spectrum Management configuration
changes MUST be performed from the master. To enforce this, the Spectrum Management
web page has a different appearance depending if you are viewing the data from the master
or slave.
144
All configuration changes are applied at the master only. These changes are then messaged
from the master to the slave. Any Spectrum Management configuration messages received at
the slave are stored in non-volatile memory. This enables both master and slave to keep
identical copies of Spectrum Management configuration data in their non-volatile memories. It
is therefore possible to swap master and slave roles on an active Point-to-Point link without
modifying Spectrum Management configuration.
Figure 84 shows an example Spectrum Management webpage as seen from the master.
Figure 85 shows an example Spectrum Management webpage as seen from the slave. It
should be noted that the key configuration attributes are not available on the slave web page.
NOTE
These examples are for 15 MHz operation; other channel bandwidths are similar. The
width of the vertical green bar represents the channel width.
145
Figure 84 - Spectrum Management as seen from the Master
146
Figure 85 - Spectrum Management as seen from the Slave
147
7.9.5 Spectrum Management Configuration
The following section describes the user modifiable configuration accessible from the
Spectrum Management webpage (Figure 84). It is recommended that the default values are
maintained. If the user believes that the performance of the Spectrum Management algorithm
requires some modifications this should only be done after consulting the Motorola Point-to-
Point distributor or one of the system field support engineers.
The Spectrum Management page contains the following fields:
Page Refresh Period

The page refreshes automatically according to the setting entered here (in seconds).
Hopping Margin
Spectrum Management uses this margin when making a channel hop decision. If the
interference level of the target channel is lower than that of the active channel by at least the
Hopping Margin, the link will hop to the target channel. The default setting is 3 dB in non-radar
regions, or 10 dB in radar regions.
Asymmetric DFS
Only displayed in non-radar regions when i-DFS is enabled. The default configuration of
symmetric operation constrains the link to operate symmetrically, using the same transmit and
receive channels. When in symmetric mode the slave unit will always follow the master. If the
master moves to a new channel the slave will hop to the same channel. When the
Point-to-Point link is configured as an asymmetric link both the master and slave are free to
select the best channel from their own set of local interference metrics.
Only displayed in radar regions. The options are “DFS” and “DFS with i-DFS”
Hopping Period (not configurable)
The Spectrum Management algorithm evaluates the metrics every ‘Hopping Period’ seconds
(180 seconds by default) looking for a channel with lower levels of interference. If a better
channel is located, Spectrum Management performs an automated channel hop. If SNMP or
SMTP alerts are enabled an SNMP TRAP or an email alert is sent warning the system
administrator of the channel change.
Hopping Counter
This is used to record the number of channel hops. The number in the “(+)” brackets
indicates the number of channel changes since the last screen refresh.
Interference Threshold
Spectrum Management uses the interference threshold to perform instantaneous channel
hops. If the measured interference on a channel exceeds the specified threshold, then i-DFS
will instruct the wireless to immediately move to a better channel. If a better channel cannot
be found the PTP 600 Series Bridge will continue to use the current active channel. (Default –
85 dBm).
Channel Bandwidth (not configurable)
This shows the value of the variable channel bandwidth selected.
148
7.9.6 Barring Channels
Channels can only be barred / unbarred by the system administrator from the master
Spectrum Management web page. The barring / unbarring operations are disabled on the
slave web page. If an attempt to bar / unbar a channel is made at the slave, a warning dialog
is generated.
Barring/Unbarring of channels is performed by clicking the appropriate channel on the local or

peer channel spectrum plots on the master web page. Each bar / unbar attempt will be
proceeded by a confirmation dialog. It should be noted that the channel bar will take effect
immediately and is not related to the measurement quantization period.
7.9.7 Master and Slave Channel Spectrum Graphics
Spectrum Management presents its computed statistical measurements in a graphical display

on both the master and slave Spectrum Management web page.
Figure 86 - Example Spectrum Management Graphic
The X-axis shows a stylized view of the 9 or 10 selectable wireless channels. It is important
to note that adjacent channels on the display have a 10 MHz overlap. The display separates
the display of channels to help the clarity of the resultant display. The axis is labeled using the
channel center frequencies in MHz.
The Y-axis shows the interference power levels from –100 to –40 dBm.
The active channel (channel 5 in Figure 86) is always marked using hatched green and white
lines. The width of the hatching is directly proportional the channel bandwidth spectral
occupancy of the channel.
The individual channel metrics are displayed using a colored bar and an ‘I’ bar.
The colored bar represents the following channel state:
149
Table 13 - Spectrum Management change state key
The channel is currently in use, hosting the

Green Active
Point-to-Point wireless link
The channel has interference above the

Orange Interference
interference threshold
The channel has an interference level below the

interference threshold and is considered by the
Blue Available
Spectrum Management algorithm suitable for
hosting the Point-to-Point link
The system administrator has barred this channel

from use. For improved visibility, an additional red
Grey Barred
‘lock’ symbol is used to indicate that a channel is
barred.
The top of the colored bar represents the 99.9% percentile metric for specific channel.
The ‘I’ Bar is used to display the mean of means and peak of means metrics. The lower
horizontal bar represents the mean of means and the upper horizontal bar represents the
peak of means. The vertical bar is used as a visual cue to highlight the statistical spread
between the peak and the mean of the statistical distribution.
150
7.9.8 Active Channel History
The active channel history is a time series display of the channels used by the PTP 600
Series Bridge over the last 25 hours. The active channel history is activated from the main
Spectrum Management page using the ‘Active Channel History’ hyperlink. An example of the
active channel history display is shown in Figure 87. Where there are parallel entries on the
display this signifies that the wireless link occupied this channel during the measurement
period. The measurement periods are one minute (from zero to sixty minutes) and twenty
minutes from (60 minutes to twenty five hours).
Figure 87 - Active Channel History Screen
151
7.9.9 Viewing Historic Spectrum Management Metrics
Spectrum Management allows the system administrator to view the results of previous
measurement quantization periods. Holding down the shift key and clicking the appropriate
channel on the local channel spectrum plots activates this feature. This feature is available on
both the master and slave web page.
Figure 88 - Spectrum Management Time Series Plot
Figure 88 shows an example time series plot. A time series plot displays the previous 132
measurement quantization periods. If the PTP 600 Series Bridge has not been running for
132 quantization periods then only the number of measurement quantization periods that are
available are displayed.
Table 14 - Spectrum Management Time Series Key
GREEN Peak of Means interference measurement
BLACK 99.9% percentile of means interference measurement
BLUE Mean of Means interference measurement
152
7.9.10 Spectrum Management (Fixed Frequency)
The PTP 600 Series Bridge software allows a user to optionally fix transmit and receive
frequencies for a wireless link. Once configured, the spectrum management software will not
attempt to move the wireless link to a channel with lower co and adjacent channel
interference. Therefore this mode of operation is only recommended for deployments where
the installer has a good understanding the prevailing interference environment. (See Section
7.7.5 Installation Step 2 - Wireless Configuration). Care must also be taken to ensure that the
frequency allocations at each end of the link are compatible. To help the user when
identifying the mode of operation, Spectrum Management uses two visual cues. See Figure
89. The main page title identifies the mode of operation using the “Fixed Frequency Mode”
postfix and the selected channels are identified by a red capital ‘F’.
Figure 89 - Spectrum Management Fixed Frequency Screen
Channel barring is disabled in fixed frequency mode; it is not required as dynamic channel
hopping is prohibited in this mode.
153
The only controls available to the master are the Statistics Window and Interference
Threshold attributes. They will have no effect on the operation of the wireless link and will
only effect the generation of the channel spectrum graphics.
The active channel history menu is removed in this mode of operation as channel hopping is
prohibited.
Figure 90 - Spectrum Management Help Page (Fixed Frequency)
154
7.9.11 Spectrum Management Control with Radar Avoidance
When operating with Radar Avoidance enabled the following variances in operation apply:
• The words “Radar Avoidance” are appended to the “Spectrum Management” title at the
top of the screen. See Figure 91 and Figure 92.
• The only controls available to the master are the Interference Threshold attribute. This
has no effect on the operation of the wireless link and will only affect the generation of the
channel spectrum graphics. See Figure 91.
• Extra color coding of the interference histogram is provided. See Table 15.
When operating with RTTT (Road transport and Traffic Telematics) Avoidance enabled or
other regulatory restrictions on channel usage the following variances apply:
• All channels marked with a ‘no entry’ symbol with their associated statistics colored black
are the prohibited channels. See Figure 91 and Figure 92. These channels are never
used to host the wireless link, but CAC measurements are still taken so that adjacent
channel biases can be calculated correctly and so the user can see if other equipment is
in use.
Figure 91 - Spectrum Management Master Screen With Operational Restrictions
155
Figure 92 - Spectrum Management Slave Screen With Operational Restrictions
The colored bar represents the following channel state:
Table 15 - Spectrum Management Change State Key With Operational Restrictions
The channel is currently in use hosting the Point-to-Point

Green Active
wireless link
Orange Interference The channel has interference above the interference threshold
The channel has an interference level below the interference

Blue Available threshold and is considered by the Spectrum Management
algorithm suitable for hosting the Point-to-Point link
The system administrator has barred this channel from use.

Because the low signal levels encountered when a unit is
powered up in a laboratory environment prior to installation
Grey Barred
(which makes the grey of the channel bar difficult to see). An
additional red ‘lock’ symbol is used to indicate that a channel is
barred.
Impulsive Radar Interference has been detected on this

channel and the channel is unavailable for 30 minutes. At the
Radar
Red end of the 30 minute period a Channel Availability Check is
Detected
required to demonstrate no radar signals remain on this
channel before it can be used for the radio link.
156
Region This channel has been barred from use by the local region
Region Bar
Bar regulator
7.9.12 PTP 25600 Spectrum Management Example
As described in Section 17.2.6 PTP 25600 Available Spectrum Settings, the PTP 25600
frequency variant can operate in three frequency bands. Figure 93 shows an example of a
Lower Band with a 30 MHz channel bandwidth.
Figure 93 - PTP 25600 Example of Spectrum Management Page
157
7.10 Remote Management

The Remote Management page (Figure 94) allows the system administrator to configure the
remote management of the PTP 600 Series Bridge.
Figure 94 - Remote Management
158
7.10.1 Control Access to HTTP Interface
The attribute HTTP Access Enabled allows a user to stop any access to a unit via the web
interface. The default value for this control is set to “yes”, which means that the unit can be
accessed using the web interface. If the option “No” is selected, then a warning is displayed
as shown in Figure 95.
7.10.2 Control Access to Telnet Interface
The attribute HTTP Telnet Enabled allows a user to stop any access to a unit via the telnet
interface. The default value for this control is set to “yes”, which means that the unit can be
accessed using the telnet interface.
NOTE
If HTTP, Telnet and SNMP interfaces have been disabled, then the user needs to use
the Recovery image to reset IP & Ethernet Configuration back to factory defaults to
re-enable the HTTP-Telnet interfaces. SNMP can also be used to re-enable the other
interfaces if SNMP is enabled.
7.10.3 SNMP (Simple Network Management Protocol)
The industry standard remote management technique is SNMP (Simple Network

Management Protocol). The PTP 600 Series Bridge supports version 1 and version 2c of the
SNMP protocol.
7.10.4 Supported Management Information Bases (MIBS)
The PTP 600 Series Bridge SNMP stack currently supports the following MIBs:
• MIB-II, RFC-1213, The PTP 600 Series Bridge supports the ‘System Group’ and
‘Interfaces Group’.
• Bridge MIB, RFC-1493, The PTP 600 Series Bridge supports the ‘dot1dBase Group’ and
the ‘dot1dBasePortTable Group’.
• PTP 600 Series Bridge proprietary MIB
• RFC-2233 (High capacity counter) MIB
• WiMAX MIB
159
SNMP TRAPs supported:

• Cold Start
• Link Up
• Link Down
• DFS Channel Change
• DFS Impulsive Interference
Figure 95 – Warning when disabling HTTP interface
160
7.10.5 Diagnostics Alarms
A number of diagnostics alarms have been added to allow SNMP agents to receive traps and
emails if required. Refer to Section 7.2.1 Home Page Alarm Display for a description of all
these alarms. Checking the control “Enabled Diagnostic Alarms” in SNMP and/or SNTP
selects all the alarms shown in Figure 96. Users can access the sub-menu “Diagnostic
Alarms” to modify the alarms selected.
Figure 96 - Remote Management - Diagnostic Alarms
For a copy of the Motorola proprietary version 1 and version 2 MIB RFCs please consult the
installation CD
161
7.10.6 SNMP Configuration
The following SNMP configuration fields are displayed:
SNMP State
The SNMP state attribute controls the creation of the SNMP features. Changing the SNMP
state attribute requires a mandatory reboot of the unit. Only when the SNMP state is enabled
at system start-up will the SNMP processor task be created.
SNMP Enabled Traps
The SNMP Enabled Traps attribute controls which SNMP Traps the unit will send.
SNMP Community String
The SNMP community string acts like a password between the networks SNMP management
entity and the distributed SNMP clients (600 Series bridge). Only if the community string is
configured correctly on all SNMP entities can the flow of management information take place.
By convention the default value is set to ‘public’. When the community string is changed the
system requires a mandatory reboot before the new string or phrase is adopted.
SNMP Port Number
Is the port the SNMP management agent is listening to for commands from an SNMP
manager. The default value for this port number is 161.
SNMP Trap IP Address
Is the address of either the network SNMP manager or Trap receiver. When asynchronous
events (traps in SNMP terminology) are generated, the client unicasts these to this IP
Address. When the address is changed the system requires a mandatory reboot before the
setting is adopted
SNMP Trap Port Number
The SNMP Trap Port Number is the port number of either the networked SNMP manager or
Trap receiver. By convention the default value for the port number is 162. When the port
number is changed the system requires a mandatory reboot before the setting is adopted.
WiMAX Control
Enables and Disables the WiMAX (802.16) MIB. This control is only displayed when ‘Fixed
Frequency’ is selected during installation.
7.10.7 SMTP (Simple Mail Transport Protocol)
The SMTP client is an alternative method for the PTP 600 Series bridge to alert a system
administrator when there are or have been system errors:
SMTP Email Alert

This attribute controls the activation of the SMTP client.
SMTP Enabled Messages
The SMTP Enabled Messages attribute controls which email alerts the unit will send.
SMTP IP Address
The IP address of the networked SMTP server.
SMTP Port Number
The SMTP Port Number is the port number used by the networked SMTP server. By
convention the default value for the port number is 25.
162
SMTP Source Email Address

The email address used by the PTP 600 Series to log into the SMTP server. This must be a
valid email address that will be accepted by your SMTP Server.
SMTP Destination Email Address
The email address to which the PTP 600 Series bridge will send the alert messages.
7.10.8 SNTP (Simple Network Time Protocol)
The SNTP client allows the PTP 600 Series to obtain accurate date and time updates from a
networked timeserver. The system time is used for SNMP and event logging.
SNTP State
When enabled, the Remote Management web page permits the following attributes to be set:
SNTP IP Address
The IP address of the networked SNTP server.
SNTP Port Number
The port number of the networked SNTP server. By convention the default value for the port
number is 123.
SNTP Poll Interval
The period at which the SNTP client polls the server for time correction updates. Default 1
hour. If for any reason an SNTP poll fails, the client will automatically perform 3 retries before
waiting for the user defined poll period.
Time Zone
The time zone is a fixed offset from GMT that is added to the SNTP time to allow the
expression of time in all geographic time zones.
Daylight Saving
Allows a fixed offset of one hour to be added to the SNTP time in order to reflect the local
daylight saving time.
7.10.9 Setting the clock
The PTP 600 Series bridge has a system clock which can be used to supply accurate date
and time information in the absence of a SNTP server. The system clock is battery backed
and will continue to operate for several days if the PTP 600 Series bridge has been switched
off.
SNTP State
If the SNTP State is set to “Disabled”, see Figure 94, then the Remote Management web
page allows the following attributes to be set:
Set Time
Shows the current time in 24 hour mode. The three editable fields display hours minutes and
seconds.
Set Date
Displays the current date. The year, month and day can be set using the drop-down selection
boxes.
163
Time Zone
See Section 7.10.9 Setting the clock.
Daylight Saving
See Section 7.10.9 Setting the clock.
7.11 Diagnostics Plotter

To further enhance the diagnostic capabilities of the PTP 600 Series, the storage of link
performance histograms has been extended to 31. To optimize RAM (volatile memory) usage
a cascading histogram approach has been adopted. The root histogram is identical to the
histograms in earlier releases of the software, that is data is stored for one hour at a
resolution of one second. Previously, the histograms were simple cyclic buffers which never
stored more that the last one hour of data. The new cascading histogram approach daisy
chains multiple histograms together. When the first histogram fills up the overflow from the
first is used as an input to the next histogram in line. To optimize memory utilization, a
statistical analysis is performed on the overflow to reduce the amount of data to be stored. In
the case of the PTP 600 Series the cascading histograms are defined as:
• Histogram 1: 1 hour at a resolution of 1 second
• Histogram 2: 24 hours at a resolution of 1 minute
• Histogram 3: 30 Days at a resolution of 1 hour
For example, when histogram 1 fills up and starts to overflow the first minute of overflow is
analyzed and the maximum, minimum and mean over that minute are computed and inserted
into histogram 2. When histogram 2 fills up and starts to overflow the first hour of overflow is
analyzed and the maximum, minimum and mean over that hour is computed and inserted into
histogram 3. When histogram 3 starts to overflow, the overflow data is simply discarded.
164
7.11.1 Diagnostic Plotter Page
New for the PTP 600 Series is the system administration diagnostic plotter facility see Figure
97.
Figure 97 - Diagnostic Plotter
The diagnostic plotter allows the system administrator to view the cascading histogram data
in an easily accessible graphical form. The plot always displays three traces, maximum,
minimum and mean by default. The diagnostic selector allows the user to select the various
categories of histogram.
The histograms that are available are:

• Vector Error
• Rx Power
• Tx Power
• Signal Strength Ratio
• Link Loss
• Rx Data Rate
• Tx Data Rate
• Aggregate Data Rate
The diagnostic plotter uses a novel time representation in the x-axis which compresses the
timeline of the plot without sacrificing resolution.
165
The trace selection allows the user to control which traces are plotted.
As with other management pages the page refresh period can be used to interactively
monitor the wireless link.
7.11.2 CSV Download
The diagnostics Download page allows the system administrator to download snapshots of
system diagnostics.
Figure 98 - CSV Download
The following diagnostics are available:

• Vector Error
• Rx Power
• Tx Power
• Signal Strength Ratio V/H
• Link Loss
• Rx Data Rate
• Tx Data Rate
• Aggregate Data Rate
• Receive SNR
• Rx Gain
All diagnostics are extracted from the associated status and statistics web page histograms.
They are translated in a CSV file containing at most 5784 entries. These 5784 entries
comprise 3600 entries for the first hour, 1440 entries for the next 24 hours and 744 entries for
the next 31 days.
166
7.12 Change Password

This page (Figure 99) is used to change the password for the system administration (The
factory default is blank).
Figure 99 - Password Change
The password may contain any combination of characters, up to 31 characters in length.
7.13 License Key

The License Key data entry page allows the system administrator to update the PTP 600
Series bridge license key. Figure 100 shows a sample license key data entry page.
Figure 100 - Software License Key Data Entry
167
The user must enter the license key and click the ‘Validate License Key’ button to check that
the key is valid and program it to non-volatile memory.
If a valid license key is detected then the user will be presented by a system reboot screen.
Figure 101 - License Key reboot Screen
The user will then be asked to confirm the reboot (Figure 102).
168
7.14 Properties
The web page properties screen allows the user to configure the web page interface (Figure
103).
Figure 103 – Properties
The Properties page contains the following fields:
WEB Properties: Disable Front Page Login

Allows access to homepage and status page web pages without forcing a login as the system
administrator.
WEB Properties: Disable HTTP NO-CACHE META data
Removes the HTTP NO-CACHE META clause from all dynamically created web pages.
Auto Logout Timer
Configures the time, in minutes, when the system administrator is automatically logged out if
no web page activity is detected.
Distance Units
Swaps the default metric display of distance in to imperial units, for example km to Miles.
Use Long Integer Comma Formatting
Changes the format of long integers from 1000000 to 1,000,000.
169
7.15 Reboot
The reboot page allows the system administrator to perform commanded reboots of the
wireless unit. The reboot page also allows the system administrator to view a list of past
reboot reasons. The “Previous Reasons For Reset/Reboot” field has been implemented as a
drop down selection box, where the latest reason for reboot is located at the top of the list.
If the SNTP service from the remote management section above is active, or the system time
has been set, then the command reboot reason will be accompanied by the date and time at
which the reboot occurred.
Figure 104 - System Reboot
170
8 Recovery Mode
8 Recovery Mode
This section provides instructions to allow users to recover a PTP 600 link.
The Motorola PTP 600 point-to-point wireless Ethernet bridges have a special mode of
operation that allows the user to recover a unit from configuration errors or software image
corruption.

• 8.1 Entering Recovery Mode
• 8.2 Upgrade Software Image
• 8.3 Reset IP & Ethernet Configuration
• 8.4 Erase Configuration
• 8.5 Reboot
8.1 Entering Recovery Mode

Recovery mode is entered by depressing the Recovery Switch located on the underside of
the PIDU Plus while applying mains power, as shown in Section 2.7 PIDU Plus PTP
300/500/600 Series The Recovery Switch should be held in the depressed state for between
10 and 20 seconds after the application of mains power. The Ethernet LED will flash with 10
double flashes at power up (following the release of the Recovery switch).
When in recovery mode the user will be able to access the unit via the Ethernet interface. The
Ethernet interface will have its IP address set to 169.254.1.1 (or 10.10.10.10). See Section
6.5.10 Powering Up). On connection to a unit in recovery mode the following screen is
displayed (Figure 106):
Figure 106 - Recovery Mode Warning Page
171
8 Recovery Mode
Clicking on the warning page image will take the user on to the Recovery Option Page
(Figure 107).
Figure 107 - Recovery Options Page
The recovery options available are:
Upgrade Software Image

This allows the user to reload a software image. This may be the original image if software
corruption is suspected or a step back to an old image if an incorrect image has just been
loaded.
Reset IP & Ethernet Configuration back to factory defaults
This allows the user to reset the unit back to the factory defaults:
IP Address 169.254.1.1 (or 10.10.10.10)
Netmask 255.255.0.0
Gateway 169.254.1.0
Ethernet Interface Auto-negotiate, Auto-MDI/MDIX
Erase Configuration
This allows the user to erase the unit’s entire configuration. Executing this option will also
erase factory settings such as target MAC address, range setting, license key, etc.
Reboot
This allows the user to reboot the unit. This option must be executed after resetting the IP &
Ethernet configuration or erasing the configuration detailed above.
Software Version
This is the software version of the recovery operating system permanently installed during
manufacture.
172
8 Recovery Mode
Recovery Reason
Indicates the reason the unit is operating in Recovery mode. Possible reasons are “Recovery
button active” or “Invalid or corrupt image”
MAC Address
The MAC address shown here is the MAC address of the unit programmed during
manufacture.
8.2 Upgrade Software Image

The first step (Figure 107) is to use the ‘Browse’ button to locate the software image to be
downloaded. Once located the user should press the “Upgrade Software Image” button to
start the software download process.
During software download, progress is indicated by a pair of progress bars (Figure 108).
Figure 108 - Software Download Progress Indicator Page
When the download is complete a page is displayed indicating the status of the software
download (Figure 109).
Figure 109 - Software Download Complete Page
173
8 Recovery Mode
After carefully checking that correct image has been downloaded the user should reboot the
unit by pressing the “Reboot Wireless Unit” button. The user will then be presented with a pop
up box asking them to confirm the action (Figure 110).
The unit will now reboot. Providing the unit configuration is still intact the unit should restart in
normal operational mode and the link should recover. Should the unit or link fail to recover the
user should refer to Section 9 Troubleshooting.
174
8 Recovery Mode
8.3 Reset IP & Ethernet Configuration

To reset IP & Ethernet configuration back to factory defaults the user should press the “Reset
IP & Ethernet Configuration back to factory defaults” button on the “Recovery Options” page
(Figure 107). The user will now be presented with a pop up box asking them to confirm the
1
action (Figure 111).
Figure 111 - Confirm Reset to Factory Default Pop Up
On confirmation the following page will be displayed (Figure 112). The user should now
reboot the unit by pressing the “Reboot” button.
Figure 112 - IP and Ethernet Erased Successfully page
175
8 Recovery Mode
The user will now be presented with a pop up box asking them to confirm the action (Figure
113).
The unit will now reboot. The unit should now start up in normal mode but with the IP address
set to 169.254.1.1 and the Ethernet interface set to auto-negotiate and auto-MDI/MDIX.
Should the unit fail to start up the user should refer to Section 9 Troubleshooting.
8.4 Erase Configuration

To erase the unit’s configuration the user should press the “Erase Configuration” button on
the “Recovery Options” page (Figure 107). The user will now be presented with a pop up box
asking them to confirm the action (Figure 114).
Figure 114 - Confirm Erase Configuration Pop Up
176
8 Recovery Mode
On confirmation the following page will be displayed (Figure 115). The user should now
reboot the unit by pressing the “Reboot” button.
Figure 115 - Erase Configuration Successful Page
177
8 Recovery Mode
The user will now be presented with a pop up box asking them to confirm the action (Figure
116)
Figure 116 – Erase Configuration - Reboot Confirmation Pop Up
The unit will now reboot. The unit should now start up in normal mode but with all
configuration erased. Should the unit fail to start up the user should refer to Section 9
Troubleshooting.
178
8 Recovery Mode
8.5 Reboot
This option can be used to reboot the unit. The user will now be presented with a pop up box
asking them to confirm the action (Figure 117).
Figure 117 – Recovery - Reboot Confirmation Pop Up
The unit will now reboot. The unit should now start up in normal operational mode. Should the
unit fail to start up the user should refer to Section 9 Troubleshooting.
179
9 Troubleshooting
9 Troubleshooting
This section provides instructions for identifying and correcting faults in a PTP 600 link.
Perform the following procedures either on a newly installed link, or on an operational link if
communication is lost:
1. Test the hardware at one end of the link, as described in Section 9.1 Test Link End
Hardware.
2. Test the hardware at the other end of the link, as described in Section 9.1 Test Link
End Hardware.
3. Test the radio link, as described in Section 9.2 Test Radio Link.
4. If an installation has been struck by lightning, see Section 9.3 Lightning Strike.
9.1 Test Link End Hardware

When the link end hardware (PIDU Plus, LPU, ODU and cabling) has been installed, start it
and test it by following this procedure:
1. Connect the RJ45 from the ODU (or LPU if fitted) to the PIDU Plus and apply mains
or battery power to the PIDU Plus. The green Power LED should illuminate
continuously.
2. After 45 seconds, the yellow Ethernet LED should be observed starting with 10 slow
flashes.
3. Connect the RJ45 from the LAN port of the PIDU Plus to the network. The yellow
Ethernet LED should blink randomly as traffic passes through.
4. If the Power and Ethernet LEDs do not illuminate correctly, test the link end as
described in the flowchart (Figure 118) and detailed test procedures (Sections 9.1.1
to 9.1.7).
5. If a GPS synchronization unit has been installed, but one or more of its status LEDs
are not illuminated, refer to Section 9.1.8 Test GPS Synchronization Unit.
180
9 Troubleshooting
Figure 118 – Link End Hardware Test Flowchart
Start
Is the green No Is the power No

power LED LED Power LED is
on solid? flashing? Off (9.1.1)
Yes
Yes
Power LED
Flashes (9.1.2)
Did the No
Ethernet LED did
Ethernet
not Flash 10 Times
LED flash 10
(9.1.3)
Yes
Is Ethernet No Is there any No

No Ethernet
activity now Ethernet
Activity (9.1.4)
normal? activity?
Yes
Yes
Irregular
Ethernet
Is Ethernet No Activity (9.1.5)
Connection is not
connection
1000 BaseT
1000 BaseT?
(9.1.6)
Yes
Test RJ45 Resistance

(9.1.7)
181
9 Troubleshooting
9.1.1 Power LED is Off
1. Remove the power lead from the PIDU Plus and test that the power source (mains or
56 V battery) is working.
2. If the main or battery power supply is working, open the flap on the left hand side of
the PIDU Plus and remove the RJ45 ODU cable from the PIDU Plus.
3. If the Power LED does not illuminate when the RJ45 ODU cable is removed:
i. Measure the voltage across the +55 V and 0 V pads inside the PIDU Plus
flap. An incorrect reading indicates that the PIDU Plus is short-circuited.
ii. Measure the impedance across the Power connector. An incorrect reading
indicates that the PIDU Plus is short-circuited.
iii. If both of the above tests are successful, it is likely that the PIDU Plus Power
LED is faulty.
4. If the Power LED does illuminate when the RJ45 ODU cable is removed:
i. Remove the jumper (J905) found inside the PIDU Plus flap.
ii. Measure the current with an ammeter placed across the two jumper pins. It
should be 10 mA with the ODU disconnected. An incorrect ammeter reading
indicates that the PIDU Plus is faulty.
5. If all tests so far have succeeded:

i. Reconnect the RJ45 ODU cable to the PIDU Plus.
ii. Measure the current with an ammeter placed across the two jumper pins. It
should be in the range 300 mA to 1 A with the ODU connected.
iii. If the ammeter reading is too high, the ODU may be drawing too much
power, or the ODU may be short-circuited.
iv. If the ammeter reading is too low, the PIDU Plus may be supplying too little
power.
182
9 Troubleshooting
9.1.2 Power LED is Flashing
If the green Power LED flashes, perform the following tests on the RJ45 cable that connects
the PIDU Plus to the LPU or ODU:
1. Check that pins 4&5 and 7&8 are not crossed with pins 1&2 and 3&6.
2. Check that the resistance between pins 1&8 is greater than 100K ohms.
3. If either test fails, replace or repair the RJ45 cable.
9.1.3 Ethernet LED did not Flash 10 Times
When the PIDU Plus is connected to the power supply and the green Power LED illuminates,
there should be a 45 second delay, following which the yellow Ethernet LED should flash 10
times. If the Ethernet LED did not flash 10 times, perform the following tests on the RJ45
cable that connects the PIDU Plus to the LPU or ODU:
1. Check that the wiring to pins 4&5 and 7&8 is correct. For example, the wiring to pins
4 and 7 may be crossed.
2. If an LPU is installed, it can be used to check that power is available on the cable to
the ODU. The connections can be accessed by rotating the LPU lid as shown in
Figure 119. The Lid nut only needs to be slacken, do not remove. Test point P1 on
the LPU PCB corresponds to pin 1 on the RJ45 etc. An indication of power on the
Ethernet cable is also provided inside the LPU: the LED PWR1 should illuminate but
LED PWR2 should not.
183
9 Troubleshooting
Figure 119 - PTP LPU Test Points
If either test fails, replace or repair the RJ45 cable.
9.1.4 No Ethernet Activity
If the Ethernet LED did flash 10 times but then went off, check that the RJ45 connection from
the LAN port of the PIDU Plus to the PC is working. If the PC connection is working, perform
the following test on the RJ45 cable that connects the PIDU Plus to the LPU or ODU:
1. Check that the wiring to pins 1&2 and 4&6 is correct. For example, the wiring
to pins 1 and 3 may be crossed.
2. If this test fails, replace or repair the RJ45 cable.
184
9 Troubleshooting
9.1.5 Irregular Ethernet Activity
The yellow Ethernet LED should blink randomly as normal traffic passes through. If the
Ethernet LED flashes irregularly, for example there is a short flash followed by a long flash,
this indicates that the ODU has booted in recovery mode. The causes may be installation
wiring or a corrupt ODU software load. For more information, see Section 8 Recovery Mode.
9.1.6 Connection is not 1000 BaseT
If the Ethernet connection to the network is only 10/100 BaseT, when 1000 BaseT is
expected, perform the following test on the RJ45 cable that connects the PIDU Plus to the
LPU or ODU:
1. Check that the wiring to pins 4&5 and 7&8 is correct. For example, the wiring to pins
4 and 7 may be crossed.
2. If this test fails, replace or repair the RJ45 cable.
9.1.7 Test RJ45 Resistance
If the above procedures fail to diagnose the issue, there may be a fault in the wiring of the
RJ45 cable that connects the ODU (or LPU) to the PIDU Plus. Unplug this cable from the
PIDU Plus, then perform the following test procedure:
1. Check the cable resistance between pins 1&2, 3&6, 4&5 and 7&8 at the RJ45. Check
against column 2 in Table 16. Resistances for each pair should be within 1 ohm of
each other.
2. Check the cable resistance between pins 1&3 and 4&7 at the RJ45. Check against
columns 3 and 4 respectively in Table 16.
3. Ensure that there is greater than 100K ohms between pin 1 and ODU ground for all
cable lengths.
4. Ensure that there is greater than 100K ohms between pin 8 and ODU ground for all
cable lengths.
5. If GPS is not fitted, ensure that there is greater than 100K ohms between pin 1 and
pin 8 for all cable lengths. If GPS is fitted, ensure there is greater than 2K ohms
between pin 1 and pin 8.
185
9 Troubleshooting
Table 16 - Resistance Table Referenced To The RJ45 at the PIDU Plus+
Resistances should fall within + or -10% of the stated values.

CAT-5 Resistance between Resistance between Resistance
Length pins 1&2, 3&6 , 4&5 and pins 1&3 (ohms) between pins 4&7
(Meters) pins 7&8 (ohms) (ohms)
0 0.8 1.0 1.6
10 2.7 2.7 3.3
20 4.6 4.4 5.0
30 6.5 6.1 6.7
40 8.3 7.8 8.4
50 10.2 9.5 10.1
60 12.1 11.2 11.8
70 14.0 12.9 13.5
80 15.8 14.6 15.2
90 17.7 16.3 16.9
100 19.6 18.0 18.6
150 29.0 26.5 27.1
200 38.4 35.0 35.6
250 47.7 43.5 44.1
300 57.1 52.0 52.6
186
9 Troubleshooting
9.1.8 Test GPS Synchronization Unit
The GPS synchronization unit, if installed, is located between the ODU and the LPU (Figure
27 and Figure 28). Use the status LEDs (Figure 120) to test the GPS unit.
Figure 120 - GPS Synchronization Unit
To troubleshoot the GPS synchronization unit, perform the following test procedure:
1. Power supply: Check that the +3.3V and RF_ON LEDs are lit, indicating that the
GPS is receiving power. If they are not lit, confirm that all link end hardware (PIDU
Plus, LPU, ODU and cabling) tests have been performed.
2. Synchronization: Approximately 2 minutes after powering on, the GPS_FIX LED

should be lit. If it is not, ensure the GPS is at a height of at least 1.8m above the
ground, where there is an unobstructed path to the sky.
3. Timing: When the GPS_FIX LED lights up, the PPS_OUT LED should begin blinking
faintly at one pulse per second, indicating that sync is being generated. If does not,
replace or repair the GPS synchronization unit.
187
9 Troubleshooting
9.2 Test Radio Link
9.2.1 No Activity
If there is no communication over the radio link and the unit at the other end of the link can be
managed on its local network, the following procedure should be adopted:
If there is no wireless activity then the configuration should be checked. It is essential that the
following items are correct:
1. Check for Alarm conditions on Home page.
2. Check that the software at each end of the link is the same version.
3. Check that the Target Mac address has been correctly configured at each end of the
link.
4. Check Range.
5. Check Tx Power.
6. Check License keys to ensure that both units are the same product variant.
7. Check Master/Slave status for each unit and ensure that one unit is Master and the
other unit is slave.
8. Check that the link has not been further obscured or the ODU misaligned.
9. Check the DFS page at each end of the link and establish that there is a quiet
wireless channel to use.
If there are no faults found in the configuration and there is absolutely no wireless signal, retry
the installation procedure. If this does not work then the ODU may be faulty.
188
9 Troubleshooting
9.2.2 Some Activity
If there is some activity but the link is unreliable or does not achieve the data rates required
then:
1. Check that the interference has not increased using the i-DFS measurements.
2. If a quieter channel is available check that it is not barred.
3. Check that the path loss is low enough for the communication rates required.
4. Check that the ODU has not become misaligned.
9.3 Lightning Strike

If a link end installation is struck by lightning, perform the following diagnostic procedure:
1. Perform the tests specified in Section 9.1 Test Link End Hardware. Ensure that the
PIDU Plus is working and that the resistances are correct as specified in 9.1.7 Test
RJ45 Resistance.
2. If the ODU is not working, power off the ODU and both LPUs and return them to
Motorola.
3. If the ODU is working but there is suspicion of damage to the LPU, then take the
LPUs down and take the covers off, inspect for damage, test the big diode for short
circuit and test all other diodes for forward voltage.
189
10 Connectorized PTP 600 Series Bridge
This section details the changes and additional features relevant to the connectorized version
of the PTP 600 Series products.

• 10.1 Product Description
• 10.2 Software/Features
• 10.3 Deployment Considerations
• 10.4 Link Budget
• 10.5 Regulatory Issues with Connectorized Units
• 10.6 Antenna Choices
• 10.7 Installation
• 10.8 Additional Lightning Protection
10.1 Product Description
10.1.1 Hardware
The Connectorized PTP 600 Series Bridge is a variant designed to provide the system
integrator and installer with the ability to provide extra capability to cope with very difficult
radio links compared to the PTP 600 Series Integrated model. The variant allows the use of a
variety of externally mounted antennas, either Flat Plate or Dish, which have higher gains
than provided by the integrated antenna that is normally used.
190
Figure 121 – Connectorized 600 Series Bridge Outdoor Unit
10.1.2 Antenna
The antenna choices for the Connectorized PTP 58600 and 54600 are described in Section
10.6 Antenna Choices.
10.2 Software/Features
This section only describes the areas where functionality is modified for the connectorized
variant. For details of the functionality that is common to the integrated and connectorized
variants, see Section 7 Web Page Reference.
10.2.1 Status Page
The link loss calculation presented on the Status Page of the management interface has to be
modified to allow for the increased antenna gains at each end of the link. The manufacturing
process of the Connectorized 600 Series Bridge configures the standard hardware of the unit
for use with external antennas. The installer is prompted, as part of the installation process, to
enter the gain of the external antenna(s) and cable losses at each end of the link.
Peer-to-peer messaging is used to pass the effective antenna gain to each end of the link so
that the link loss calculations can be correctly computed.
191
Figure 122 - Connectorized 600 Series bridge Status Page
10.2.2 Configuration Pages
The Configuration web page for the connectorized variant is shown in Figure 123. The
parameters Antenna Gain, Cable Loss and EIRP are specific to the connectorized variant.
Figure 123 - Connectorized 600 Series bridge ‘System Configuration’ Page
192
10.2.3 Installation Pages
The installer is prompted to enter the Antenna Gain and Cable Loss (Connectorized PTP 600
Series Bridge to antenna) at each end of the link. The Installation Pages for the
connectorized version are shown as Figure 124 to Figure 126.
Figure 124 - Connectorized PTP 600 Series Bridge ‘Installation’ Page
Antenna Gain
Gain of the antenna you are connecting to the unit, see Section 10.6 Antenna Choices.
193
Cable Loss
Loss in the cable between the ODU and the antenna.
NOTE
If there is a significant difference in length of the antenna cables for the two antenna
ports, then the average value should be entered.

Is used to configure the PTP 600 Series Bridge Spectrum Management features, see Section
7.9 Spectrum Management for more details. i-DFS is the abbreviation for intelligent Dynamic
Frequency Selection, which continually monitors the spectrum looking for the channel with the
lowest level of on channel and co-channel interference. Fixed frequency mode allows the
installer to fix the Transmit and receive frequencies on the units. The frequencies may be
configured symmetrically or asymmetrically.
194
Figure 125 - Connectorized 600 Series bridge ‘Confirm Installation’ Page
EIRP
The Confirm Installation Page displays the EIRP (Effective Isotropic Radiated Power), which
describes the strength of the radio signal leaving the wireless unit. This allows the operator to
verify that their link configuration (Max Transmit Power, Antenna Gain and Cable Loss) do not
cause the link to exceed any applicable regulatory limit.
195
Figure 126 - Connectorized 600 Series bridge ‘Disarm Installation’ Page
196
10.3 Deployment Considerations

The majority of radio links can be successfully deployed with the PTP 600 Series. It should
only be necessary to use external antennas where the LINKPlanner indicates marginal
performance for a specific link – for example when the link is heavily obscured by dense
woodland on an NLOS link or extremely long LOS links (>80km or >50 miles) over water.
The external antennas can be either dual-polarization (as the integrated antenna) or two
single polarized antennas can be used in a spatially diverse configuration. It is expected that
the dual-polarization antennas would normally be used to simplify the installation process;
spatially diverse antennas may provide additional fade margin on very long LOS links where
there is evidence of correlation of the fading characteristics on Vertical and Horizontal
polarizations.
10.4 Link Budget

An estimate of the link budget for a specific application can be obtained by using the Motorola
Systems link estimation tools. For more information see the Motorola web site.
10.5 Regulatory Issues with Connectorized Units

Installations must conform to any applicable local regulations for the Equivalent Isotropic
Radiated Power (EIRP).
Ensuring compliance becomes more complex when the connectorized unit is used with
external antennas which may be locally sourced. With higher gain external antennas fitted,
the Maximum Transmit power may need to be reduced for operation in specific countries.
In some regions, operation of the PTP 600 products is constrained by EIRP limits. For more
information on these limits, see Section 4.2 Licenses and Region Codes.
When operating with external antennas, the installer/operator has to set the maximum
transmit power to ensure that the EIRP limit is not exceeded. Use this formula:
Maximum Transmit Power Allowed = EIRP Limit – Antenna Gain + Cable Losses
Set the power to the 1dB value lower than the actual value calculated.
197
10.5.1 Cable Losses (FCC Regions Only)
The FCC approval for the product is based on tests with a cable loss between the units of not
less than 1.2 dB at 5.8 GHz. The use of lower cable losses would result in the installation
being outside the FCC rules. As an indication, 1.2 dB of cable loss corresponds to the
following cable lengths excluding connector losses (source: Times Microwave).
Table 17 - Cable Losses per Length
Length for 1.2dB Cable Loss at 5.8 GHz

Cable
(ft) (m)
LMR100 1.9 0.6
LMR200 4.6 1.4
LMR300 7.25 2.2
LMR400 11.1 3.4
LMR600 16.5 5.0
10.6 Antenna Choices

The main selection criterion is the required antenna gain. The secondary criterion is the ease
of mounting and alignment. For example, the Radio Waves Parabolic dishes are supplied with
a mount that allows adjustment for alignment independent of the actual antenna mounting.
This type of antenna is much easier to align than those that have to be rotated around the
mounting pole for alignment.
In non-FCC regions, antenna choice is not restricted, but any region specific EIRP limit must
be obeyed by reducing the maximum Transmit power, see Section 4.2 Licenses and Region
Codes.
In FCC regions, antenna choice is restricted as described in Sections 17.6.8 PTP 54600 FCC
Antenna Restrictions and 17.7.8 PTP 58600 FCC Antenna Restrictions.
The maximum permitted antenna gain depends upon product variant and channel bandwidth,
as specified in Sections 17.5.4 PTP 49600 Radio System Specifications, 17.6.4 PTP 54600
Radio System Specifications and 17.7.4 PTP 58600 Radio System Specifications.
198
10.7 Installation
The section covers the generic installation instructions for the Connectorized versions of the
PTP 600 Series point-to-point wireless Ethernet bridges. The actual installation procedure will
depend on antenna choice, cable choice, required antenna separation etc.
Sections 17.6.8 PTP 54600 FCC Antenna Restrictions and 17.7.8 PTP 58600 FCC Antenna
Restrictions show a wide variety of antennas that can be used with the Connectorized PTP
600 Series bridge.
10.7.1 Cables and Connectors
Cables should be selected using the above criteria. However it should be noted that a cable
of a type similar to LMR400 is a lot more difficult to handle and route than a cable of a type
similar to LMR100.
Motorola recommends the use of weatherproof connectors -- preferably, ones that come
supplied with adhesive lined heat shrink sleeve that is fitted over the cable/connector
interface.
The connectors required at the Connectorized 600 Series bridge end of the antenna cables
are N-Type Male.
The connectors required at the antenna end of the antenna cables is dependant on the
antenna type chosen.
10.7.2 Tools
The tools required for mounting a Connectorized 600 Series bridge unit are the same as
those required for an Integrated 600 Series bridge detailed in Section 6.3 Preparation. The
tools required for mounting the antennas are specific to the antenna chosen. The installer
should refer to the antenna manufacturer’s instructions.
199
10.7.3 Miscellaneous supplies
The following miscellaneous supplies will be required:

• Cable ties, cable cleats – for securing cables
• Self-amalgamating tape – to weatherproof the RF connectors
• PVC tape – for additional protection of the RF connectors and securing cables
10.7.4 Mounting the Connectorized 600 Series Bridge
A Connectorized 600 Series bridge is shipped with the same bracket as supplied with an
Integrated unit. Details on the use of this bracket can be found in Section 2.12 Mounting
Brackets. The PTP 600 Series Bridge should be mounted in a position that gives it maximum
protection from the elements, but still allows easy access for making off the various
connections and applying the recommended weatherproofing.
When using dual polar antennas the Connectorized 600 Series bridge should be mounted in
such a position as to minimize the cable length, keeping losses to a minimum, taking into
account the minimum cable lengths required by the FCC regulations, see Section 17.7.8 PTP
58600 FCC Antenna Restrictions.
When using separate antennas the Connectorized 600 Series Bridge should be mounted in
such a position as to minimize both cable runs between the unit and the antennas. It is not
necessary to mount the Connectorized 600 Series Bridge at the mid point between the
antennas.
10.7.5 Mounting the antennas
The Antennas should be mounted according to the manufacturer’s instructions. Actual

antenna position will depend on the available mounting positions and link requirements. It
may be necessary to mount the antennas 20m apart or at a certain distance from the ground
to get the desired results.
200
10.7.6 Alignment Process
When aligning antennas deployed with a Connectorized 600 Series bridge unit it may not be
possible to hear the alignment tone emanating from the unit. In this case it may be necessary
for a second installer to assist in the operation. Alternatively, it may be possible to extend the
tube on the supplied stethoscope to give a longer reach.
NOTE
Fine antenna alignment can sometimes be achieved by tightening and loosening the
bolts on either side of the antenna mounting bracket, rather than trying to turn the
whole bracket on the mounting pole.
10.7.7 Aligning Dual Polar Antennas
The process for aligning a dual polar antenna is the same as aligning an Integrated unit with
an integrated antenna. This procedure is detailed in Section 6.6.1 Aligning the PTP 600
Series Bridge ODUs.
10.7.8 Aligning Separate Antennas
When using separate antennas to achieve spatial diversity, one should be mounted with
Horizontal polarization and the other with Vertical polarization.
The following steps should be followed:
1. Mount the Antennas
2. Mount the connectorized version of the PTP 600 Series Bridge unit
3. Route and make off the ends of the Antenna cables
4. Connect the antenna cables at the antennas
5. Connect one of the antenna cables at the Connectorized version of the PTP 600
Series bridge unit.
6. Connect the Connectorized 600 Series Bridge ODU to PIDU Plus cable and configure
the unit as described in Section 6.5 Connecting Up.
7. Align the connected antenna using the tones as described in Section 6.6.1 Aligning
the PTP 600 Series Bridge ODUs.
201
8. Connect the other antenna to the Connectorized 600 Series bridge.
9. Disconnect the cable to the already aligned antenna.
10. Align the second antenna using the tones as described in Section 6.6.1 Aligning the
PTP 600 Series Bridge ODUs.
11. Re-connect the second antenna to the Connectorized 600 Series bridge. You will
notice the tone pitch increase as you re-connect the second antenna due to the
additional received signal.
12. Use the relevant status web pages to check that you are getting the results you
expect from your link planning.
13. Complete the installation as detailed below.
10.7.9 Completing the Installation
The installation should be completed by checking all mounting nuts bolts and screws,
securing all cables and weatherproofing the installation.
CAUTION
Finally tightening the antenna mountings may cause the antenna alignment to be
altered, due to distortion in the mounting bracket caused by action of tightening. It is
recommended that the installation tone be left turned on (armed) during this process
so that any movement can be noticed and counteracted by tightening the other side
of the bracket.
10.7.10 Antenna Cable Fixing
Cables should be secured in place using cable ties, cleats or PVC tape. Care should be
taken to ensure that no undue strain is placed on the connectors on both the Connectorized
600 Series bridge and the Antennas and also to ensure that the cables do not flap in the
wind. Flapping cables are prone to damage and induce unwanted vibrations in the mast to
which the units are attached.
202
10.7.11 Antenna Connection Weatherproofing
Where a cable connects to an antenna or unit from above, a drip loop should be left to ensure
that water is not constantly channeled towards the connector.
Figure 127 - Forming a Drip Loop
All joints should be weatherproofed using self-amalgamating tape. It is recommended that a

layer of PVC tape be placed over the self-amalgamating tape to protect the joint while the
self-amalgamating tape cures and gives additional protection. Figure 128 shows this
diagrammatically for the PTP 600 Series bridge end of the antenna cables. If the antenna
manufacturer has not supplied guidance on this matter, the same technique should be
employed at the antenna end of the cable.
Figure 128 - Weatherproofing the Antenna Connections
203
10.8 Additional Lightning Protection

The following guidelines should be applied in addition to those described in Section 5
Lightning Protection.
10.8.1 ODU Mounted Outdoors
Where the ODU is mounted outdoors and is mounted some distance from the antenna, it is
advisable to add additional grounding by utilizing Andrew Assemblies (such as Andrew Type
223158 www.andrew.com) as shown in Figure 129.
Figure 129- Additional Grounding When Using Connectorized Units
NOTE
Refer to instructions contained in the Andrew grounding kit for correct installation, or if
instructions are missing, refer to:
http://awapps.commscope.com/catalog/product_details.aspx?id=15832&tab=2
204
10.8.2 ODU Mounted Indoors
Where the ODU is mounted indoors, lightning arrestors should be deployed where the
antenna cables enter the building as shown in Figure 130.
Figure 130 - Lightning Arrestor Mounting
The lighting arrestors should be ground bonded to the building ground at the point of entry.
Motorola recommends Polyphaser LSXL-ME or LSXL lighting arrestors. These should be
assembled as show in Figure 131.
Figure 131 - Polyphaser Assembly
205
11 TDD Synchronization Installation and Configuration
This section describes the installation and configuration of the TDD synchronization feature.

• 11.1 Benefits of TDD Synchronization
• 11.2 TDD Synchronization Installation
• 11.3 TDD Synchronization Configuration
11.1 Benefits of TDD Synchronization

When planning a network of links, a key consideration is the interference that exists between
the links. TDD synchronization is a feature which eliminates two specific interference
mechanisms, namely interference between Master and Master and interference between
Slave and Slave.
One example which highlights the need for TDD synchronization is the case where a number
of links are required from a single mast. Without TDD synchronization, high levels of
interference will occur between the units on the mast due to their close proximity. By enabling
TDD synchronization, interference between these units is eliminated if all are of the same
type. The recommendation is for all units on a mast to be configured as Masters. The
maximum number of links on a mast depends on the customer requirements such as required
throughput, link availability, available spectrum, maximum EIRP, bandwidth, channel
separation and the longest link. However, in some cases, it may even be possible to re-use
radio channels on the same mast which would not be possible without TDD synchronization.
In summary, by eliminating interference between units of a like type, TDD synchronization
increases network capacity by increasing frequency re-use and increasing the density of links
across the network.
206
11.2 TDD Synchronization Installation
11.2.1 Recommended Kit
The recommended GPS Sync installation kit includes the following:

• GPS Sync Unit from MemoryLink (see Figure 132), with three attached terminated
Ethernet and Sync cables and cable glands (2) which connect directly to a PTP 600
Series ODU.
• Mounting bracket and mounting bracket bolts
• Outdoor rated UV resistant cable tie
• GPS Sync Unit User Manual.
In addition to the hardware mentioned above, it is recommended to have an appropriate

lightning protection (PTP LPU as described in Section 12.6 Lightning Protection and E1/T1).
NOTE
Refer to GPS Sync Unit User manual for details on the lengths of cables used to
connect the GPS Sync Unit to the ODU and PTP LPU.
Figure 132 - GPS Synchronization Unit
207
11.2.2 GPS Sync Unit Connections
Figure 133 shows the inside of the GPS Sync Unit and Figure 134 is a diagram that shows
how to connect the GPS Sync Unit to the ODU and the Lightning protection unit.
Figure 133 - GPS Synchronization Unit Connections
Figure 134 - TDD Sync - PTP600 Deployment Diagram
208
11.2.3 Complete GPS Sync Unit Installation
Figure 135 shows an example of mast installation using lightning protection and a GPS Sync
Unit.
Figure 135- GPS Synchronization Unit Complete Installation
209
11.3 TDD Synchronization Configuration

TDD synchronization is enabled and configured during the installation process of the link.
11.3.1 TDD Synchronization Enable
Figure 136 shows how to enable TDD Synchronization.
Figure 136 - Enabling TDD Synchronization Feature
When TDD Synchronization is enabled, the following restrictions apply:

• Ranging Mode and Target Range are disabled.
• Link Symmetry is forced to ‘1:1’ operation only.
210
11.3.2 TDD Synchronization Configuration
When TDD Synchronization is enabled, there is an extra installation screen (“TDD

Synchronization”, Figure 137).
Figure 137 - Configure TDD Synchronization
The data required to populate this screen will shortly be available in PTP LINKPlanner v1.4.
The TDD Synchronization screen provides the following controls:
Max Burst Duration

The maximum duration of the burst opportunity. Select a value in the range 726 to 2176
microseconds.
TDD Frame Duration
Select a value in the range 1730 to 6410 microseconds.
TDD Frame Offset
The delay of the start of the TDD frame from the epoch of the external timing reference. This
permits the design of synchronized networks in which the phase of the TDD frame is
independent from the fundamental master/slave function. This change allows more flexibility
in selecting the location of master ODUs. Enter a value in the range from zero to one
microsecond less than the TDD Frame Duration.
Slave Receive To Transmit Gap
The duration of the gap between receive and transmit at the slave ODU.
211
TDD Holdover Mode

(Master only). Two values: “Strict” and “Best Effort”. If a PTP 600 master ODU is configured
for a TDD Holdover Mode set to “Strict”, then it will not transmit when synchronization is lost.
On the other hand, a link configured for TDD Holdover Mode set to “Best Effort” will
synchronize when a reference signal is available, but will otherwise use best efforts to operate
in unsynchronized fashion.
TDD Holdover Duration
(Master only). Default value 10 minutes, maximum 60 minutes. Specifies duration of holdover
period following loss of the external timing reference for TDD synchronization.
212
11.3.3 Confirm Settings and Reboot ODU
When all the parameters have been entered, then the user can commit the values to the unit
and reboot. Figure 138 shows the list of the installation parameters.
Figure 138 - Confirm TDD Synchronization Configuration Parameters
213
11.3.4 TDD Synchronization Status
The Status Page displays the TDD Synchronization status for the link.
If TDD Synchronization is not enabled, the Attribute is set to “TDD Synchronization Inactive”
and the Value is set to “Timing System Not Connected”.
If TDD Synchronization is enabled and the installation is rebooted, the Attribute is set to “TDD
Synchronization Status” and the Value is set to one of the following:
• Locked: (Figure 139)
• Holdover:
• Holdover (Not Connected)
• Acquiring Lock
• No Timing Reference
• Timing System Not Connected (Figure 140)
• Initialising
Figure 139 - Status Page - TDD Enabled and Synchronized
214
Figure 140 - Status Page - TDD Enabled and Not Synchronized
215
11.3.5 Disarm ODU Following TDD Sync Configuration
Figure 141 - Disarm Following TDD Synchronization
CAUTION
In a synchronized network, links MUST be configured separately before bringing the
whole network up.
216
12 E1/T1 Installation Guide
This section describes the installation and configuration of the E1/T1 interface.

• 12.1 E1/T1 Connection Diagrams
• 12.2 Connecting the E1/T1 Cable to the ODU
• 12.3 Disconnecting the E1/T1 Cable
• 12.4 Routing the Cable
• 12.5 Customer Cable Termination
• 12.6 Lightning Protection and E1/T1
• 12.7 Testing the E1/T1 Installation
NOTE
The maximum cable length between the ODU and the customers terminating
equipment is 200m (656 feet) for E1/T1.
12.1 E1/T1 Connection Diagrams

The E1/T1 cable should be assembled as described in Section 2.10 Cables and Connectors.
This procedure applies to the ODU termination, but it must be repeated for the customer
equipment end of the cable when the cable is terminated with an RJ45.
12.1.1 T568B Color Coding
The T568B color coding used in RJ45 E1/T1 cables is illustrated in Figure 142 and Figure
143. The telecoms connection pin outs are specified in Table 18.
Figure 142 - RJ45 Pin Connection (T568B Color Coding)
217
Figure 143 - Cable Connection Diagram (T568B Color Coding)
Table 18 - Telecoms Connection Pin Out
Telecoms Connector Pinout Signal Name
Pin 1 E1T1A_TX-
Pin 2 E1T1A_TX+
Pin 3 E1T1A_RX-
Pin 4 E1T1B_TX-
Pin 5 E1T1B_TX+
Pin 6 E1T1A_RX+
Pin 7 E1T1B_RX-
Pin 8 E1T1B_RX+
12.1.2 Connections at the ODU and Patch Panel
The E1/T1 connections at the ODU and patch panel are illustrated in Figure 144.
218
Figure 144 - E1-T1 Connections at the ODU and Patch Panel
219
12.1.3 Balancing Signals
The balancing of E1/T1 120 Ohm signals is illustrated in Figure 145.
Figure 145 - Two E1-T1-120 Ohms signal Balanced to PTP600 Interface
220
12.2 Connecting the E1/T1 Cable to the ODU

Looking at the back of the unit with the cable entry at the bottom, the PTP 600 Series Bridge
E1/T1 connection is the first hole on the left (Figure 146) and is labeled E1/T1.
Figure 146 - PIDU Plus and E1-T1 Connexion
221
The procedure for connecting the E1/T1 cable to the ODU is described in Figure 147. It is
often easier to carry out this procedure on the ground or a suitable surface prior to mounting
the ODU. Ensure no power is connected to the PIDU Plus or present in the cable before
connecting the ODU.
Figure 147 - Connecting the E1/T1 to the ODU
Step 1: Assemble the cable as described in

Section 2.10 Cables and Connectors. Step 2: Insert the RJ45 connector making sure
that the locking tab snaps home.
Step 3: Screw in the body of the weather

proofing gland and tighten. Step 4: Screw on the clamping nut and tighten.
CAUTION
Do not over tighten the glands as the internal seal and structure may be damaged.
See Figure 37 for an example of an over tightened cable gland.
222
12.3 Disconnecting the E1/T1 Cable

Should it be necessary to disconnect the E1/T1 cable at the ODU, this can be achieved by
removing the weatherproofing gland and depressing the RJ45 locking tab with a small
screwdriver as shown in Figure 148.
Figure 148 - Disconnecting the ODU
12.4 Routing the Cable

After connecting the cable to the ODU it can be routed and secured using standard cable
routing and securing techniques. When the cable is in place it can then be cut to the desired
length.
12.5 Customer Cable Termination

The two channels can be separated by means of a patch panel which may include Baluns for
transmission over 75 Ohm co-axial unbalanced lines. Such equipment should conform to the
requirements of C.C.I.T.T. G703. An example of a Balun is shown below. It allows the
transmit and receive data carried over a 75 Ohm cable to be converted to a balanced form for
transmission over a 120 Ohm signal balanced twisted pair.
Figure 149 - Example of a Balun
223
12.6 Lightning Protection and E1/T1
12.6.1 Overview
Section 5 Lightning Protection contains the requirements for the Motorola PTP 600 Series
deployment. For E1/T1, an extra grounding cable is supplied to connect the other PTP-LPU to
the ODU ground. This section details the additional requirements for the deployment of
E1/T1.
12.6.2 Recommended Additional Components for E1/T1 Installation.
For a description of Zone A and Zone B refer to Section 5 Lightning Protection.
Table 19 - Protection Requirements
Component Zone A Zone B
Earth ODU Mandatory Mandatory
Screen Cable Mandatory Mandatory
Lightning Protection Unit PTP LPU at ODU Mandatory Mandatory
Earth Cable at Building Entry Mandatory Mandatory
Lightning Protection Unit PTP LPU at Building Mandatory Mandatory

Entry
Refer to Section 5.5 LPU Installation Diagrams to see how the components of PTP 600 sites
with E1/T1 are installed and connected. This section also lists the recommended components
for each type of installation.
224
12.7 Testing the E1/T1 Installation

If you have opted to fit a Lightning Protection Unit, it should be tested as described in Section
5.4 LPU Installation.
Test the telecoms links by performing loopback connections as described in Section 7.5.5
Telecoms Configuration.
12.7.1 Pre-Power Testing
Before connecting your E1/T1 source, check the following resistances:
Check the cable resistance between pins 3 & 6 (Green/White & Green) and 7 & 8
(Brown/White & Brown). Check against Table 20 column 2.
Check the cable resistance between pins 1 & 2 (Orange/White & Orange) and 4 & 5 (Blue &
Blue/White). Check against Table 20 column 3.
Table 20 - Resistance Table Referenced To the E1/T1 Source

CAT-5 Length (Meters) Resistance between pins Resistance between pins
3 & 6 and pins 7 & 8 1 & 2 and pins 4 & 5
(ohms) (ohms)
0 0.8 1.3
10 2.5 3.0
20 4.2 4.7
30 5.9 6.4
40 7.6 8.2
50 9.3 9.8
60 11.0 11.5
70 12.7 13.2
80 14.4 14.9
90 16.1 18.2
100 17.8 18.3
225
13 Data Rate Calculations
This section provides instructions, tables and graphs to allow calculation of the data rate
capacity that can be provided by alternative PTP 600 configurations.

• 13.1 Data Rate Defined
• 13.2 Calculation Procedure and Example
• 13.3 Data Throughput Capacity
• 13.4 Range Adjustment Curves
13.1 Data Rate Defined

The data rate capacity of a PTP link is defined as the maximum end-to-end Ethernet
throughput (including Ethernet headers) that it can support. It is assumed that Ethernet
frames are 1500 octet. Data rate capacity is determined by the following factors:
• Product variant (PTP 600 Full or Lite)
• Link Symmetry
• Link Mode Optimization (IP or TDM)
• Modulation Mode
• Channel Bandwidth
• Link Range
13.2 Calculation Procedure and Example
13.2.1 Procedure
To calculate the data rate capacity of a PTP 600 link, follow this procedure:
Use the tables in Section 13.3 to look up the data throughput capacity rates (Tx, Rx and Both)
for the required combination of:
• Link Symmetry
• Link Mode Optimization
• Modulation Mode
• Channel Bandwidth
The tables in Section 13.3 contain data rates for PTP 600 Full only. If the ODUs are PTP 600
Lite, divide the data rates in Section 13.3 by 2.
226
The tables in Section 13.3 contain data rates for links of zero range. Use the curves in
Section 13.4 to look up the Throughput Factor that must be applied to adjust the data rates
for the actual range of the link.
Multiply the data rates by the Throughput Factor to give the throughput capacity of the link.
NOTE
There is a small difference between the rates for IP and TDM because there is
fragmentation in TDM (for low priority traffic) which causes the throughput to be
reduced buy approximately 1% compared to the IP mode.
13.2.2 Example
Suppose that the link characteristics are:

• Product variant = PTP 600 Lite
• Link Symmetry = 1:1
• Link Mode Optimization = TDM
• Modulation Mode = 64QAM 0.92 Dual
• Channel Bandwidth = 10 MHz
• Link Range = 60 km
Applying the calculation procedure:
Use Table 22 to look up the data throughput capacity rates:

• Tx = 41.41 Mbits/s
• Rx = 41.41 Mbits/s
• Both = 82.81 Mbits/s
Divide these rates by 2 to give PTP 600 Lite rates:

Use Figure 158 to look up the Throughput Factor for 1:1, TDM and Link Range 60 km. The
factor is 0.86.
227
Multiply the rates from Step 2 by the Throughput Factor from Step 3 to give the throughput
capacity of the link:
13.3 Data Throughput Capacity

Table 21, Table 22, Table 23, Table 24 and Table 25 show the data throughput rates
(Mbits/s) that are achieved when two PTP 600 Full ODUs are linked and the link distance
(range) is 0 km. Use the curves in Section 13.4 to adjust these figures to allow for link range.
NOTE
When using these tables, be aware of the factors that affect data throughput, as listed
below.
Data throughput capacity is restricted by the following factors:

• PTP 600 Lite data rates are half the PTP 600 Full rates given in this section.
• Modulation Mode “256QAM 0.81 dual” is not available in all product variants and channel
bandwidths.
• Throughput for Link Symmetry 2:1 is the same as that for 1:2, but the Tx and Rx data
rates are swapped.
• The data rates for Adaptive symmetry apply to the most asymmetric case where the link
has significant offered traffic in one direction only. The data rates for Adaptive symmetry
with bidirectional offered traffic are the same as those for Link Symmetry = 1:1 with Link
Optimization = IP.
228
Table 21 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = IP
At zero range. All rates are in Mbit/s.

30 MHz 20 MHz 15 MHz
Modulation Mode
Tx Rx Both Tx Rx Both Tx Rx Both
256QAM 0.81 dual 150.01 150.01 300.02 100.06 100.06 200.12 75.37 75.37 150.74
64QAM 0.92 dual 126.39 126.39 252.78 84.30 84.30 168.61 63.50 63.50 127.01
64QAM 0.75 dual 103.28 103.28 206.57 68.89 68.89 137.78 51.89 51.89 103.79
16QAM 0.87 dual 80.35 80.35 160.70 53.60 53.60 107.19 40.37 40.37 80.74
16QAM 0.63 dual 57.76 57.76 115.52 38.53 38.53 77.06 29.02 29.02 58.04
256QAM 0.81 single 75.00 75.00 150.01 50.03 50.03 100.06 37.69 37.69 75.37
64QAM 0.92 single 63.19 63.19 126.39 42.15 42.15 84.30 31.75 31.75 63.50
64QAM 0.75 single 51.64 51.64 103.28 34.45 34.45 68.89 25.95 25.95 51.89
16QAM 0.87 single 40.17 40.17 80.35 26.80 26.80 53.59 20.18 20.18 40.37
16QAM 0.63 single 28.88 28.88 57.76 19.26 19.26 38.53 14.51 14.51 29.02
QPSK 0.87 single 20.09 20.09 40.17 13.40 13.40 26.79 10.09 10.09 20.18
QPSK 0.63 single 14.44 14.44 28.88 9.63 9.63 19.26 7.25 7.25 14.51
BPSK 0.63 single 7.22 7.22 14.44 4.81 4.81 9.63 3.63 3.63 7.25
229
(continued)
10 MHz 5 MHz
Modulation Mode
Tx Rx Both Tx Rx Both
256QAM 0.81 dual 50.11 50.11 100.21 24.22 24.22 48.43
64QAM 0.92 dual 42.22 42.22 84.43 20.40 20.40 40.80
64QAM 0.75 dual 34.50 34.50 69.00 16.67 16.67 33.34
16QAM 0.87 dual 26.84 26.84 53.68 12.97 12.97 25.94
16QAM 0.63 dual 19.29 19.29 38.59 9.32 9.32 18.65
256QAM 0.81 single 25.05 25.05 50.11 12.11 12.11 24.21
64QAM 0.92 single 21.11 21.11 42.21 10.20 10.20 20.40
64QAM 0.75 single 17.25 17.25 34.50 8.34 8.34 16.67
16QAM 0.87 single 13.42 13.42 26.84 6.48 6.48 12.97
16QAM 0.63 single 9.65 9.65 19.29 4.66 4.66 9.32
QPSK 0.87 single 6.71 6.71 13.42 3.24 3.24 6.48
QPSK 0.63 single 4.82 4.82 9.64 2.33 2.33 4.66
BPSK 0.63 single 2.41 2.41 4.82 1.16 1.16 2.33
230
Table 22 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = TDM

Modulation Mode
256QAM 0.81 dual 140.87 140.87 281.74 96.01 96.01 192.02 72.92 72.92 145.83
64QAM 0.92 dual 118.69 118.69 237.38 80.89 80.89 161.78 61.43 61.43 122.87
64QAM 0.75 dual 96.99 96.99 193.98 66.10 66.10 132.21 50.20 50.20 100.41
16QAM 0.87 dual 75.45 75.45 150.91 51.43 51.43 102.85 39.06 39.06 78.11
16QAM 0.63 dual 54.24 54.24 108.48 36.97 36.97 73.94 28.08 28.08 56.15
256QAM 0.81 single 70.43 70.43 140.87 48.00 48.00 96.01 36.46 36.46 72.91
64QAM 0.92 single 59.34 59.34 118.69 40.44 40.44 80.89 30.72 30.72 61.43
64QAM 0.75 single 48.49 48.49 96.99 33.05 33.05 66.10 25.10 25.10 50.20
16QAM 0.87 single 37.73 37.73 75.45 25.71 25.71 51.42 19.53 19.53 39.05
16QAM 0.63 single 27.12 27.12 54.24 18.48 18.48 36.97 14.04 14.04 28.07
QPSK 0.87 single 18.86 18.86 37.72 12.85 12.85 25.71 9.76 9.76 19.52
QPSK 0.63 single 13.56 13.56 27.12 9.24 9.24 18.48 7.02 7.02 14.03
BPSK 0.63 single 6.78 6.78 13.56 4.62 4.62 9.24 3.51 3.51 7.02
231
(continued)
10 MHz 5 MHz
Modulation Mode
Tx Rx Both Tx Rx Both
256QAM 0.81 dual 49.14 49.14 98.29 24.22 24.22 48.43
64QAM 0.92 dual 41.41 41.41 82.81 20.40 20.40 40.80
64QAM 0.75 dual 33.84 33.84 67.67 16.67 16.67 33.34
16QAM 0.87 dual 26.32 26.32 52.64 12.97 12.97 25.94
16QAM 0.63 dual 18.92 18.92 37.84 9.32 9.32 18.65
256QAM 0.81 single 24.57 24.57 49.14 12.11 12.11 24.21
64QAM 0.92 single 20.70 20.70 41.40 10.20 10.20 20.40
64QAM 0.75 single 16.92 16.92 33.83 8.34 8.34 16.67
16QAM 0.87 single 13.16 13.16 26.32 6.48 6.48 12.97
16QAM 0.63 single 9.46 9.46 18.92 4.66 4.66 9.32
QPSK 0.87 single 6.58 6.58 13.16 3.24 3.24 6.48
QPSK 0.63 single 4.73 4.73 9.46 2.33 2.33 4.66
BPSK 0.63 single 2.36 2.36 4.73 1.16 1.16 2.33
232

Modulation Mode
256QAM 0.81 dual 198.58 99.29 297.88 133.42 66.71 200.12 100.50 50.25 150.74
64QAM 0.92 dual 167.31 83.66 250.97 112.41 56.20 168.61 84.67 42.33 127.01
64QAM 0.75 dual 136.73 68.36 205.09 91.86 45.93 137.78 69.19 34.59 103.79
16QAM 0.87 dual 106.37 53.18 159.55 71.46 35.73 107.19 53.83 26.91 80.74
16QAM 0.63 dual 76.47 38.23 114.70 51.37 25.68 77.06 38.70 19.35 58.04
256QAM 0.81 single 99.29 49.64 148.94 66.71 33.35 100.06 50.25 25.12 75.37
64QAM 0.92 single 83.66 41.83 125.48 56.20 28.10 84.30 42.33 21.17 63.50
64QAM 0.75 single 68.36 34.18 102.54 45.93 22.96 68.89 34.59 17.30 51.89
16QAM 0.87 single 53.18 26.59 79.77 35.73 17.86 53.59 26.91 13.46 40.37
16QAM 0.63 single 38.23 19.11 57.35 25.68 12.84 38.53 19.35 9.67 29.02
QPSK 0.87 single 26.59 13.29 39.88 17.86 8.93 26.79 13.46 6.73 20.18
QPSK 0.63 single 19.11 9.56 28.67 12.84 6.42 19.26 9.67 4.84 14.51
BPSK 0.63 single 9.56 4.78 14.33 6.42 3.21 9.63 4.84 2.42 7.25
233
(continued)
This combination is not available with Channel Bandwidth 5 MHz.
10 MHz
Modulation Mode
Tx Rx Both
256QAM 0.81 dual 66.38 33.19 99.56
64QAM 0.92 dual 55.92 27.96 83.88
64QAM 0.75 dual 45.70 22.85 68.55
16QAM 0.87 dual 35.55 17.78 53.33
16QAM 0.63 dual 25.56 12.78 38.34
256QAM 0.81 single 33.19 16.59 49.78
64QAM 0.92 single 27.96 13.98 41.94
64QAM 0.75 single 22.85 11.42 34.27
16QAM 0.87 single 17.78 8.89 26.66
16QAM 0.63 single 12.78 6.39 19.17
QPSK 0.87 single 8.89 4.44 13.33
QPSK 0.63 single 6.39 3.19 9.58
BPSK 0.63 single 3.19 1.60 4.79
234

Modulation Mode
256QAM 0.81 dual 193.06 96.53 289.58 130.66 65.33 195.99 98.83 49.42 148.25
64QAM 0.92 dual 162.66 81.33 243.98 110.08 55.04 165.13 83.27 41.63 124.90
64QAM 0.75 dual 132.92 66.46 199.38 89.96 44.98 134.94 68.05 34.02 102.07
16QAM 0.87 dual 103.41 51.70 155.11 69.98 34.99 104.98 52.94 26.47 79.40
16QAM 0.63 dual 74.34 37.17 111.50 50.31 25.15 75.46 38.05 19.03 57.08
256QAM 0.81 single 96.53 48.26 144.79 65.33 32.66 97.99 49.42 24.71 74.12
64QAM 0.92 single 81.33 40.66 121.99 55.04 27.52 82.56 41.63 20.82 62.45
64QAM 0.75 single 66.46 33.23 99.69 44.98 22.49 67.47 34.02 17.01 51.03
16QAM 0.87 single 51.70 25.85 77.55 34.99 17.49 52.49 26.47 13.23 39.70
16QAM 0.63 single 37.17 18.58 55.75 25.15 12.58 37.73 19.03 9.51 28.54
QPSK 0.87 single 25.85 12.92 38.77 17.49 8.75 26.24 13.23 6.62 19.85
QPSK 0.63 single 18.58 9.29 27.87 12.58 6.29 18.86 9.51 4.76 14.27
BPSK 0.63 single 9.29 4.64 13.93 6.29 3.14 9.43 4.76 2.38 7.13
235
(continued)

10 MHz
Modulation Mode
Tx Rx Both
256QAM 0.81 dual 66.38 33.19 99.56
64QAM 0.92 dual 55.92 27.96 83.88
64QAM 0.75 dual 45.70 22.85 68.55
16QAM 0.87 dual 35.55 17.78 53.33
16QAM 0.63 dual 25.56 12.78 38.34
256QAM 0.81 single 33.19 16.59 49.78
64QAM 0.92 single 27.96 13.98 41.94
64QAM 0.75 single 22.85 11.42 34.27
16QAM 0.87 single 17.78 8.89 26.66
16QAM 0.63 single 12.78 6.39 19.17
QPSK 0.87 single 8.89 4.44 13.33
QPSK 0.63 single 6.39 3.19 9.58
BPSK 0.63 single 3.19 1.60 4.79
236
Table 25 – Data Throughput for PTP 600 Full, Link Symmetry = Adaptive, Link Optimization =
IP

Modulation Mode
256QAM 0.81 dual 236.95 59.23 296.18 148.53 49.51 198.03 112.12 37.37 149.49
64QAM 0.92 dual 199.63 49.91 249.54 125.14 41.71 166.85 94.46 31.49 125.95
64QAM 0.75 dual 163.14 40.78 203.92 102.26 34.09 136.35 77.19 25.73 102.92
16QAM 0.87 dual 126.91 31.73 158.64 79.55 26.52 106.07 60.05 20.02 80.07
16QAM 0.63 dual 91.24 22.81 114.04 57.19 19.06 76.25 43.17 14.39 57.56
256QAM 0.81 single 118.47 29.62 148.09 74.26 24.75 99.02 56.06 18.68 74.74
64QAM 0.92 single 99.82 24.95 124.77 62.57 20.85 83.42 47.23 15.74 62.97
64QAM 0.75 single 81.57 20.39 101.96 51.13 17.04 68.17 38.59 12.86 51.46
16QAM 0.87 single 63.46 15.86 79.32 39.78 13.26 53.03 30.02 10.01 40.03
16QAM 0.63 single 45.62 11.40 57.02 28.59 9.53 38.12 21.58 7.19 28.78
QPSK 0.87 single 31.73 7.93 39.66 19.89 6.63 26.51 15.01 5.00 20.01
QPSK 0.63 single 22.81 5.70 28.51 14.30 4.76 19.06 10.79 3.60 14.39
BPSK 0.63 single 11.40 2.85 14.25 7.15 2.38 9.53 5.39 1.80 7.19
237
Table 25 – Data Throughput for PTP 600 Full, Link Symmetry = Adaptive, Link Optimization = IP
(continued)
10 MHz
Modulation Mode
Tx Rx Both
256QAM 0.81 dual 66.38 33.19 99.56
64QAM 0.92 dual 55.92 27.96 83.88
64QAM 0.75 dual 45.70 22.85 68.55
16QAM 0.87 dual 35.55 17.78 53.33
16QAM 0.63 dual 25.56 12.78 38.34
256QAM 0.81 single 33.19 16.59 49.78
64QAM 0.92 single 27.96 13.98 41.94
64QAM 0.75 single 22.85 11.42 34.27
16QAM 0.87 single 17.78 8.89 26.66
16QAM 0.63 single 12.78 6.39 19.17
QPSK 0.87 single 8.89 4.44 13.33
QPSK 0.63 single 6.39 3.19 9.58
BPSK 0.63 single 3.19 1.60 4.79
238
13.4 Range Adjustment Curves

Use these curves to look up the link Range and find the Throughput Factor that must be
applied to adjust the 0 km data throughput rates for the required combination of Channel
Bandwidth, Link Symmetry, Link Optimization, DFS and Link Range (km).
Table 26 – Range Adjustment Characteristics
Channel Link Link DFS Range See Figure

Bandwidth Symmetry Optimization Adjustment
Curve
30 MHz 1:1 IP A Figure 150
TDM B Figure 151
2:1 IP C Figure 152
TDM D Figure 153
Adaptive IP E Figure 154
20 MHz 1:1 IP L Figure 159
TDM N Figure 160
2:1 IP L Figure 159
TDM O Figure 161
Adaptive IP C Figure 152
15 MHz 1:1 IP F Figure 155
TDM G Figure 156
2:1 IP None F Figure 155
FCC or C Figure 152

ETSI
TDM None H Figure 157
FCC or C Figure 152

ETSI
Adaptive IP A Figure 150
239
Channel Link Link DFS Range See Figure

Bandwidth Symmetry Optimization Adjustment
Curve
10 MHz 1:1 IP F Figure 155
TDM K Figure 158
2:1 IP L Figure 159
TDM L Figure 159
Adaptive IP L Figure 159
5 MHz 1:1 IP, TDM C Figure 152
240
Figure 150 – PTP 600 Range Adjustment for Data Rates, Curve A
Figure 151 – PTP 600 Range Adjustment for Data Rates, Curve B
241
Figure 152 – PTP 600 Range Adjustment for Data Rates, Curve C
Figure 153 – PTP 600 Range Adjustment for Data Rates, Curve D
242
Figure 154 – PTP 600 Range Adjustment for Data Rates, Curve E
Figure 155 – PTP 600 Range Adjustment for Data Rates, Curve F
243
Figure 156 – PTP 600 Range Adjustment for Data Rates, Curve G
Figure 157 – PTP 600 Range Adjustment for Data Rates, Curve H
244
Figure 158 – PTP 600 Range Adjustment for Data Rates, Curve K
Figure 159 – PTP 600 Range Adjustment for Data Rates, Curve L
245
Figure 160 – PTP 600 Range Adjustment for Data Rates, Curve N
246
Figure 161 – PTP 600 Range Adjustment for Data Rates, Curve O
247
14 AES Encryption
14 AES Encryption
This section describes how to encrypt a PTP 600 link.

• 14.1 Encryption Standard Used
• 14.2 Upgrading for Link Encryption
• 14.3 Configuring Link Encryption
• 14.4 Wireless Link Encryption FAQ
14.1 Encryption Standard Used

The Motorola PTP 600 Series bridges support link encryption using the NIST approved
Advanced Encryption Standard, HFIPS-197 H. This standard specifies AES (Rijndael) as a
UT
FIPS-approved symmetric encryption algorithm that may be used by U.S. Government

organizations (and others) to protect sensitive information.
14.2 Upgrading for Link Encryption

Link Encryption is not available in the standard PTP 600 Series system. A license key to
enable link encryption can be purchased from your Motorola Point-to-Point Distributor or
Solutions Provider. AES can be activated on receipt of the activation on the Motorola
Systems Support Page.
There are two levels of encryption that are available to purchase:

• 128-bit
• 128 and 256-bit
Option 1 allows the user to encrypt all traffic sent over the wireless link using 128-bit
encryption. Option 2 allows the user to encrypt traffic using either 128 or 256-bit encryption.
The configuration process for both encryption variants is identical except for the selection of
algorithm. The following configuration example is for a 256-bit encryption key.
14.3 Configuring Link Encryption

After purchasing AES encryption for the PTP 600 Series wireless link, two new license keys
will be issued, one for each end of the wireless link. The following configuration process gives
a step by step guide to enabling AES link encryption on a PTP 600 Series bridge.
248
14 AES Encryption
14.3.1 License Keys
The first step when configuring link encryption is to enter the new license keys in both 600
Series wireless units.
Figure 162 shows the license key data entry screen. This screen can only be accessed by the
system administrator. If you do not have access to the PTP 600 Series system administration
pages then please contact your designated system administrator.
Figure 162 – AES Software License Key Data Entry
Configuring link encryption will necessitate a 600 Series bridge service outage. Therefore it is
recommended that the configuration process be scheduled during an appropriate period of
low link utilization.
249
14 AES Encryption
Motorola recommends the following process for entering new license keys and minimizing
service outage:
1. Open two browsers, one for each end of the link
2. Navigate to the ‘License Key’ data entry page for each end of the link
3. Enter the license keys and click the ‘Validate license key’ button at each end of the
link. This will allow the software to validate the license key prior to the system reset.
(DO NOT CLICK ARE YOU SURE POPUP DIALOG)
4. When both license keys have been successfully validated, confirm the reboot for both
ends of the link. The software is designed to allow five seconds so that a user can
command both ends of the link to reset before the wireless link drops.
The link will automatically re-establish.
14.3.2 Encryption Mode and Key
Entering the license keys only does not initialize AES link encryption. Link encryption can only
be enabled via the Configuration or Installation pages. Motorola recommends that the
Configuration page Figure 163 be used to configure AES link encryption.
250
14 AES Encryption
Figure 163 – AES Configuration Data Entry Page
To enter AES link encryption configuration, follow this procedure:
1. Open two browsers, one for each end of the link
2. Navigate to the ‘Configuration’ data entry page for each end of the link
3. At both ends of the link select the ‘AES (Rijndael)’ Encryption Algorithm required.
4. At both ends of the link enter ether an 128-bit or 256-bit encryption key. Note the key
consists of 32/64 case insensitive hexadecimal characters. The same Key must be
entered at both ends of the link. Failure to enter the same key will cause the link to
fail.
5. Submit configuration on both ends of the link, but do not reboot.
6. Reboot both ends of the link Figure 164. The software is designed to allow five
seconds so that a user can command both ends of the link to reboot before the
wireless link drops.
251
14 AES Encryption
Figure 164 - Configuration Reboot Screen
14.4 Wireless Link Encryption FAQ
14.4.1 Encryption data entry fields are not available
Check that the correct license key has been inserted into the unit. The current license key is
displayed on the ‘License Key’ data entry page.
14.4.2 Link fails to bridge packets after enabling link encryption
If the wireless link status on the status web page indicates that the link is ‘Searching’, and you
can browse to the local end of the link but not to the remote end, then check that the same
encryption algorithm and key have been entered at both ends of the link. Failure to enter the
same algorithm and key will result in received packets not being decrypted correctly.
14.4.3 Loss of AES following downgrade
When downgrading (using Recovery software image 05-01 onwards) to an earlier version of
software that does not support AES, the unit will indicate that the region code is invalid. The
user will be required to re-install correct software (supplied when AES key was activated) and
reboot the unit.
252
15 Remote Software Upgrade by TFTP
This section describes how to upgrade the PTP 600 software remotely using Trivial FTP
(TFTP) triggered by SNMP.
To perform a remote software upgrade, follow this procedure:
1. Set the following tFTP attributes:
tFTPServerIPAddress: The IP address of the TFTP server from which the TFTP
software upgrade file Name will be retrieved. For example, to set the TFTP server IP
address for unit 10.10.10.10 to 10.10.10.1:
snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.5.0 a

10.10.10.1
tFTPServerPortNumber: This setting is optional. The port number of the TFTP server
from which the TFTP software upgrade file name will be retrieved (default=69).
tFTPSoftwareUpgradeFileName: The filename of the software upgrade to be loaded

from the TFTP server. For example, to set the TFTP software upgrade filename on
10.10.10.10 to "B1095.dld":
snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.7.0 s

B1095.dld
tFTPStartSoftwareUpgrade: Write '1' to this attribute to start the TFTP software upgrade
process. The attribute will be reset to 0 when the upgrade process has finished. Example:
snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.8.0 i

1
253
2. Monitor the values of the following tFTP attributes:
tFTPSoftwareUpgradeStatus: The current status of the TFTP software upgrade

process. Values:
• idle(0)
• uploadinprogress(1)
• uploadsuccessfulprogrammingFLASH(2)
• upgradesuccessfulreboottorunthenewsoftwareimage(3)
• upgradefailed(4).
Example:
snmpget_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.9.0
tFTPSoftwareUpgradeStatusText: This describes the status of the TFTP software

upgrade process, including any error details. Example:
tFTPSoftwareUpgradeStatusAdditionalText: Used if tFTPSoftwareUpgradeStatusText

is full and there are more than 255 characters to report. Additional text describing the
status of the TFTP software upgrade process, including any error details. Example:
3. When the upgrade is complete, reboot the ODU to run the newly loaded software image.
See Section 8.5 Reboot.
254
16 Legal Notices
16 Legal Notices
This section provides legal notices including software license agreements.
CAUTION
Intentional or unintentional changes or modifications to the equipment must not be
made unless under the express consent of the party responsible for compliance. Any
such modifications could void the user’s authority to operate the equipment and will
void the manufacturer’s warranty.
• 16.1 Motorola Inc. End User License Agreement
• 16.2 Hardware Warranty in U.S.
• 16.3 Limit of Liability
16.1 Motorola Inc. End User License Agreement

In connection with Motorola’s delivery of certain proprietary software or products
containing embedded or pre-loaded proprietary software, or both, Motorola is willing to
license this certain proprietary software and the accompanying documentation to you
only on the condition that you accept all the terms in this End User License Agreement
(“Agreement”).
IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE
PRODUCT OR INSTALL THE SOFTWARE. INSTEAD, YOU MAY, FOR A FULL REFUND,
RETURN THIS PRODUCT TO THE LOCATION WHERE YOU ACQUIRED IT OR PROVIDE
WRITTEN VERIFICATION OF DELETION OF ALL COPIES OF THE SOFTWARE. ANY
USE OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO USE ON THE PRODUCT,
WILL CONSTITUTE YOUR ACCEPTANCE TO THE TERMS OF THIS AGREEMENT.
16.1.1 Definitions
In this Agreement, the word “Software” refers to the set of instructions for computers, in
executable form and in any media, (which may include diskette, CD-ROM, downloadable
internet, hardware, or firmware) licensed to you. The word “Documentation” refers to
electronic or printed manuals and accompanying instructional aids licensed to you. The word
“Product” refers to Motorola’s MOTOwi4™ fixed wireless broadband devices for which the
Software and Documentation is licensed for use.
255
16 Legal Notices
16.1.2 Grant of License
Motorola, Inc. (“Motorola”) grants you (“Licensee” or “you”) a personal, nonexclusive, non-
transferable license to use the Software and Documentation subject to the Conditions of Use
set forth in Section 16.1.3 Conditions of Use and the terms and conditions of this Agreement.
Any terms or conditions relating to the Software and Documentation appearing on the face or
reverse side of any purchase order, purchase order acknowledgment or other order
document that are different from, or in addition to, the terms of this Agreement will not be
binding on the parties, even if payment is accepted.
16.1.3 Conditions of Use
Any use of the Software and Documentation outside of the conditions set forth in this
Agreement is strictly prohibited and will be deemed a breach of this Agreement.
1. Only you, your employees or agents may use the Software and Documentation. You
will take all necessary steps to insure that your employees and agents abide by the
terms of this Agreement.
2. You will use the Software and Documentation (i) only for your internal business
purposes; (ii) only as described in the Software and Documentation; and (iii) in strict
accordance with this Agreement.
3. You may use the Software and Documentation, provided that the use is in
conformance with the terms set forth in this Agreement.
256
16 Legal Notices
4. Portions of the Software and Documentation are protected by United States copyright
laws, international treaty provisions, and other applicable laws. Therefore, you must
treat the Software like any other copyrighted material (for example, a book or musical
recording) except that you may either: (i) make 1 copy of the transportable part of the
Software (which typically is supplied on diskette, CD-ROM, or downloadable internet),
solely for back-up purposes; or (ii) copy the transportable part of the Software to a PC
hard disk, provided you keep the original solely for back-up purposes. If the
Documentation is in printed form, it may not be copied. If the Documentation is in
electronic form, you may print out 1 copy, which then may not be copied. With regard
to the copy made for backup or archival purposes, you agree to reproduce any
Motorola copyright notice, and other proprietary legends appearing thereon. Such
copyright notice(s) may appear in any of several forms, including machine-readable
form, and you agree to reproduce such notice in each form in which it appears, to the
extent it is physically possible to do so. Unauthorized duplication of the Software or
Documentation constitutes copyright infringement, and in the United States is
punishable in federal court by fine and imprisonment.
5. You will not transfer, directly or indirectly, any product, technical data or software to
any country for which the United States Government requires an export license or
other governmental approval without first obtaining such license or approval.
257
16 Legal Notices
16.1.4 Title; Restrictions
If you transfer possession of any copy of the Software and Documentation to another party
outside of the terms of this agreement, your license is automatically terminated. Title and
copyrights to the Software and Documentation and any copies made by you remain with
Motorola and its licensors. You will not, and will not permit others to: (i) modify, translate,
decompile, bootleg, reverse engineer, disassemble, or extract the inner workings of the
Software or Documentation, (ii) copy the look-and-feel or functionality of the Software or
Documentation; (iii) remove any proprietary notices, marks, labels, or logos from the Software
or Documentation; (iv) rent or transfer all or some of the Software or Documentation to any
other party without Motorola’s prior written consent; or (v) utilize any computer software or
hardware which is designed to defeat any copy protection device, should the Software and
Documentation be equipped with such a protection device. If the Software and
Documentation is provided on multiple types of media (such as diskette, CD-ROM,
downloadable internet), then you will only use the medium which best meets your specific
needs, and will not loan, rent, lease, or transfer the other media contained in the package
without Motorola’s written consent. Unauthorized copying of the Software or Documentation,
or failure to comply with any of the provisions of this Agreement, will result in automatic
termination of this license.
16.1.5 Confidentiality
You acknowledge that all Software and Documentation contain valuable proprietary
information and trade secrets and that unauthorized or improper use of the Software and
Documentation will result in irreparable harm to Motorola for which monetary damages would
be inadequate and for which Motorola will be entitled to immediate injunctive relief. If
applicable, you will limit access to the Software and Documentation to those of your
employees and agents who need to use the Software and Documentation for your internal
business purposes, and you will take appropriate action with those employees and agents to
preserve the confidentiality of the Software and Documentation, using the same degree of
care to avoid unauthorized or improper disclosure as you use for the protection of your own
proprietary software, but in no event less than reasonable care.
258
16 Legal Notices
You have no obligation to preserve the confidentiality of any proprietary information that: (i)
was in the public domain at the time of disclosure; (ii) entered the public domain through no
fault of yours; (iii) was given to you free of any obligation to keep it confidential; (iv) is
independently developed by you; or (v) is disclosed as required by law provided that you
notify Motorola prior to such disclosure and provide Motorola with a reasonable opportunity to
respond.
16.1.6 Right to Use Motorola’s Name
Except as required in 16.1.3 above, you will not, during the term of this Agreement or
thereafter, use any trademark of Motorola, or any word or symbol likely to be confused with
any Motorola trademark, either alone or in any combination with another word or words.
16.1.7 Transfer
The Software and Documentation may not be transferred to another party without the express
written consent of Motorola, regardless of whether or not such transfer is accomplished by
physical or electronic means. Motorola’s consent may be withheld at its discretion and may
be conditioned upon transferee paying all applicable license fees and agreeing to be bound
by this Agreement.
16.1.8 Updates
During the first 12 months after purchase of a Product, or during the term of any executed
Maintenance and Support Agreement for the Product, you are entitled to receive Updates.
An “Update” means any code in any form which is a bug fix, patch, error correction, or minor
enhancement, but excludes any major feature added to the Software. Updates are available
for download at http://www.motowi4solutions.com/software/.
Major features may be available from time to time for an additional license fee. If Motorola
makes available to you major features and no other end user license agreement is provided,
then the terms of this Agreement will apply.
259
16 Legal Notices
16.1.9 Maintenance
Except as provided above, Motorola is not responsible for maintenance or field service of the
Software under this Agreement.
16.1.10 Disclaimer
MOTOROLA DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS,

IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. MOTOROLA
SPECIFICALLY DISCLAIMS ANY WARRANTY INCLUDING THE IMPLIED WARRANTIES OF
MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE.
THE SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS.” MOTOROLA DOES
NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT
THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE,
OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. MOTOROLA MAKES
NO WARRANTY WITH RESPECT TO THE CORRECTNESS, ACCURACY, OR
RELIABILITY OF THE SOFTWARE AND DOCUMENTATION. Some jurisdictions do not
allow the exclusion of implied warranties, so the above exclusion may not apply to you.
16.1.11 Limitation of Liability
THE TOTAL LIABILITY OF MOTOROLA UNDER THIS AGREEMENT FOR DAMAGES WILL
NOT EXCEED THE TOTAL AMOUNT PAID BY YOU FOR THE PRODUCT LICENSED
UNDER THIS AGREEMENT. IN NO EVENT WILL MOTOROLA BE LIABLE IN ANY WAY
FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL OR PUNITIVE DAMAGES OF
ANY NATURE, INCLUDING WITHOUT LIMITATION, LOST BUSINESS PROFITS, OR
LIABILITY OR INJURY TO THIRD PERSONS, WHETHER FORESEEABLE OR NOT,
REGARDLESS OF WHETHER MOTOROLA HAS BEEN ADVISED OF THE POSSIBLITY
OF SUCH DAMAGES. Some jurisdictions do not permit limitations of liability for incidental or
consequential damages, so the above exclusions may not apply to you.
260
16 Legal Notices
16.1.12 U.S. Government
If you are acquiring the Product on behalf of any unit or agency of the U.S. Government, the
following applies. Use, duplication, or disclosure of the Software and Documentation is
subject to the restrictions set forth in subparagraphs (c) (1) and (2) of the Commercial
Computer Software – Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable,
unless being provided to the Department of Defense. If being provided to the Department of
Defense, use, duplication, or disclosure of the Products is subject to the restricted rights set
forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013 (OCT 1988), if applicable. Software and Documentation may
or may not include a Restricted Rights notice, or other notice referring specifically to the terms
and conditions of this Agreement. The terms and conditions of this Agreement will each
continue to apply, but only to the extent that such terms and conditions are not inconsistent
with the rights provided to you under the aforementioned provisions of the FAR and DFARS,
as applicable to the particular procuring agency and procurement transaction.
16.1.13 Term of License
Your right to use the Software will continue in perpetuity unless terminated as follows. Your
right to use the Software will terminate immediately without notice upon a breach of this
Agreement by you. Within 30 days after termination of this Agreement, you will certify to
Motorola in writing that through your best efforts, and to the best of your knowledge, the
original and all copies, in whole or in part, in any form, of the Software and all related material
and Documentation, have been destroyed, except that, with prior written consent from
Motorola, you may retain one copy for archival or backup purposes. You may not
sublicense, assign or transfer the license or the Product, except as expressly provided in this
Agreement. Any attempt to otherwise sublicense, assign or transfer any of the rights, duties
or obligations hereunder is null and void.
16.1.14 Governing Law
This Agreement is governed by the laws of the United States of America to the extent that
they apply and otherwise by the laws of the State of Illinois.
16.1.15 Assignment
This agreement may not be assigned by you without Motorola’s prior written consent.
261
16 Legal Notices
16.1.16 Survival of Provisions
The parties agree that where the context of any provision indicates an intent that it survives
the term of this Agreement, then it will survive.
16.1.17 Entire Agreement
This agreement contains the parties’ entire agreement regarding your use of the Software
and may be amended only in writing signed by both parties, except that Motorola may modify
this Agreement as necessary to comply with applicable laws.
16.1.18 Third Party Software
The software may contain one or more items of Third-Party Software supplied by other third-
party suppliers. The terms of this Agreement govern your use of any Third-Party Software
UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH
CASE YOUR USE OF THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY
THE SEPARATE THIRD-PARTY LICENSE.
UCD SNMP
Copyright 1989, 1991, 1992 by Carnegie Mellon University, Derivative Work – 1996, 1998-
2000, Copyright 1996, 1998-2000 The regents of the University of California All Rights
reserved. Permission to use, copy, modify and distribute this software and its documentation
for any purpose and without fee is hereby granted, provided that the above copyright notice
appears in all copies and that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of CMU and The Regents of the University of
California not be used in advertising or publicity pertaining to distribution of the software
without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF
CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED. WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE
LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE. ONLY OPEN THE PACKAGE, OR USE THE SOFTWARE AND
RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. BY BREAKING
THE SEAL ON THIS DISK KIT / CDROM, OR IF YOU USE THE SOFTWARE OR RELATED
PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. IF YOU DO NOT
AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE OR RELATED PRODUCT;
INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND.
THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN
INDIVIDUAL OR ENTITY), AND MOTOROLA, INC. (FOR ITSELF AND ITS LICENSORS).
THE RIGHT TO USE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT
YOU AGREE TO THE FOLLOWING TERMS.
262
16 Legal Notices
BZIP2 License Terms

“bzip2" and associated library "libbzip2", are copyright (C) 1996-2000 Julian R Seward. All
rights reserved. Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
o Redistributions of source code must retain the above copyright notice, this list
of condition sand the following disclaimer.
o The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is
not required.
o Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
o The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
zlib.h
Interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005.
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler. This software is provided 'as-is',
without any express or implied warranty. In no event will the authors be held liable for any
damages arising from the use of this software. Permission is granted to anyone to use this
software for any purpose, including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
o The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is
not required.
o Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
o This notice may not be removed or altered from any source distribution.
Jean-loup Gailly [email protected]

Mark Adler [email protected]
263
16 Legal Notices
16.2 Hardware Warranty in U.S.

Motorola U.S. offers a warranty covering a period of one year from the date of purchase by
the customer. If a product is found defective during the warranty period, Motorola will repair
or replace the product with the same or a similar model, which may be a reconditioned unit,
without charge for parts or labor.
16.3 Limit of Liability

IN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY
DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY
OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT
(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS,
BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER
PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF MOTOROLA HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow
the exclusion or limitation of incidental or consequential damages, so the above exclusion or
limitation may not apply to you.) IN NO CASE SHALL MOTOROLA’S LIABILITY EXCEED
THE AMOUNT YOU PAID FOR THE PRODUCT.
264
17 PTP 600 Reference Information
This section describes the reference information and regulatory notices that are common to
all PTP 600 products and those that are specific to each frequency variant.

• 17.1 PTP 600 General Reference Information
• 17.2 PTP 25600 Reference Information
17.1 PTP 600 General Reference Information
17.1.1 PTP 600 System Specifications
Table 27 – PTP 600 Management Specifications
Management Specification
Power status
Status Indication Ethernet Link Status
Data activity
Web server and browser for setup
Audio tone feedback during installation , plus

Installation graphical installation tool suitable for laptop and
PDA computing devices
Web server for confirmation
Radio Performance and Management Via web server and browser, SNMP
Alarms Via configurable email alerts, SNMP
265
Table 28 – PTP 600 Ethernet Bridging Specifications
Ethernet Bridging Specification
Protocol IEEE802.1; IEEE802.1p; IEEE802.3 compatible
IEEE 802.1p (eight levels), IEEE 802.1Q, IEEE

QoS
802.1ad
10/100/1000BaseT (RJ-45), Supports MDI/MDIX
Interface
Auto Crossover
Data Rates See Section 13 Data Rate Calculations
Maximum Ethernet Frame Size 2000 bytes
NOTE
Practical Ethernet rates will depend on network configuration, higher layer protocols
and platforms used.
Over the air throughput will be capped to the rate of the Ethernet interface at the
receiving end of the link.
Table 29 – PTP 600 Physical Specifications
Integrated Specification
Dimensions Width 14.5” (370mm), Height 14.5” (370mm), Depth 3.75” (95mm)
Weight 12.1 lbs (5.5 Kg) including bracket
Connectorized Specification
Dimensions Width 12” (305mm), Height 12” (305mm), Depth 4.01” (105mm)
Weight 9.1 lbs (4.3 Kg) including bracket
266
Table 30 – PTP 600 Power Supply Specifications
Power Supply Separate power supply unit (included)
Dimensions Width 9.75” (250mm), Height 1.5” (40mm), Depth 3” (80mm)
Weight 1.9 lbs (0.864 Kg)
Power source 90 – 264 V ac, 50 – 60 Hz / 36 – 60 V dc
Power consumption 55 W max
Table 31 – PTP 600 Telecoms Interface Specifications
Telecoms Specification
2 E1 balanced 120R or 2 T1 balanced 100R over a CAT5 screened

Interfaces
twisted pair cable
Jitter and Wander Compliant with G.823/ G.824.
Surge Protection
Compliant with GR1089, EN60950, K20, K21.
and Power Cross
17.1.2 PTP 600 Safety Compliance
Table 32 – PTP 600 Safety Compliance Specifications
Region Specification
USA UL 60950
Canada CSA C22.2 No.60950
International CB certified & certificate to IEC 60950
267
17.1.3 PTP 600 EMC Immunity Compliance
Top-level Specification ETSI 301-489.
Table 33 – PTP 600 EMC Immunity Compliance Specifications
Specification Comment
EN 55082-1 Generic EMC and EMI

requirements for Europe
EN 61000-4-2: 1995 Electro Static

Testing will be carried to ensure immunity to
Discharge (ESD), Class 2, 8 kV air, 4 kV
15kV air and 8kV contact
contact discharge
EN 61000-4-3: 1995 ENV50140: 1993

(radiated immunity) 3 V/m
EN 61000-4-4: 1995 (Bursts/Transients),

Signal lines @ 0.5 kV open circuit voltage.
Class 4, 4 kV level (power lines AC & DC)
Requires screened connection to users

EN 6100045:1995, (Surge Immunity)
network
EN 61000-4-6: 1996 (Injected RF), power Signal lines, Class 3 @ 3 V RMS un-
line, Class 3 @ 10 V/m modulated.
268
17.1.4 PTP 600 Environmental Specifications
Table 34 – PTP 600 Environmental Specifications
Category Specification
ODU: -40°F (-40°C) to 140°F (+60°C)

PIDU Plus (indoor deployment): 32°F (0°C) to 104oF (+40°C)
Temperature
PIDU Plus (outdoor deployment within weatherproofed cabinet):
-40°F (-40°C) to 140°F (+60°C)
150mph Max (242kph). See Section 4.7 Wind Loading for a full
Wind Loading
description.
Humidity 100% Condensing (ODU only)
Waterproof IP65 (ODU only)
UV Exposure 10 year operational life (UL746C test evidence)
269
17.2 PTP 25600 Reference Information

This section contains reference information that is specific to the PTP 25600 frequency
variant.
17.2.1 PTP 25600 Examples of Regulatory Limits
Table 35 shows how the regulatory limits currently apply in specific countries. Operators
should note that regulations are subject to change.
Table 35 – PTP 25600 Examples of Regulatory Limits

Region Examples of Regulatory Limits 2.5 GHz
Under FCC Regulations, operation of this product is only allowed with a License
Key for Region 16 which ensures that the product will meet the requirements of
FCC FCC part 27.
Note: Spectrum in this band (2496MHz to 2690MHz) is allocated on a licensed
basis in USA.
270
17.2.2 PTP 25600 Licenses and Region Codes
PTP 25600 units may be operated in any of the regions listed in Table 36.
When shipped, PTP 25600 units are configured with a license key for Region Code 16. An
alternative license key is provided in the Deployment Guide for Region Code 18.
NOTE
For a PTP 25600 in Region Code 16, the EIRP limit is approximately 63 dBm + 10 x
Log(360/Antenna Azimuth BW). PTP25600 products are not able to exceed this EIRP
limit with any available antenna.
Table 36 – PTP 25600 Licenses and Region Codes
Region License / Channel

Code Regulation Frequencies DFS Bandwidth Max Power Notes
16 2624 - 2690 The 30MHz
FCC Upper MHz 5, 10, 15, 30 MHz 63 dBm EIRP bandwidth is not
2572 - 2614 approved in FCC
FCC Middle MHz 5, 10, 15, 30 MHz 63 dBm EIRP regions.
2496 - 2568
FCC Lower MHz 5, 10, 15, 30 MHz 63 dBm EIRP
18 Taiwan 2660 - 2690

Upper MHz 5, 10, 15 MHz 23 dBm
Taiwan 2595 - 2625
Middle MHz 5, 10, 15 MHz 23 dBm
Taiwan 2565 - 2595
Lower MHz 5, 10, 15 MHz 23 dBm
271
17.2.3 PTP 25600 Regulatory Compliance
The PTP 25600 complies with the regulations that are in force in the USA. The relevant
notifications are specified in this section.
17.2.3.1 U.S. Federal Communication Commission (FCC) Notification
This device complies with Part 27 of the US FCC Rules and Regulations. Use of this product
is limited to operators holding Licenses for the specific operating channels.
This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to Part 15E of the US FCC Rules. These limits are designed to provide
reasonable protection against harmful interference in a residential installation. This
equipment generates, uses, and can radiate radio-frequency energy and, if not installed and
used in accordance with these instructions, may cause harmful interference to radio
communications. If this equipment does cause harmful interference to radio or television
reception, which can be determined by turning the equipment on and off, the user is
encouraged to correct the interference by one or more of the following measures:
• Increase the separation between the affected equipment and the unit;
• Connect the affected equipment to a power outlet on a different circuit from that which the
receiver is connected to;
• Consult the dealer and/or experienced radio/TV technician for help.
• FCC IDs Certification Numbers are listed below:
Where necessary, the end user is responsible for obtaining any National licenses required to
operate this product and these must be obtained before using the product in any particular
country. Contact the appropriate national administrations for details on the conditions of use
for the bands in question and any exceptions that might apply.
272
17.2.4 PTP 25600 Radio System Specifications
Table 37 contains radio system specifications for the PTP 25600.
Table 37 - PTP 25600 RF Specifications
Radio Technology Specification
Lower: 2.496-2.568 GHz

RF Band Middle: 2.572-2.614 GHz
Upper: 2.618-2.690 GHz
Channel Selection Manual selection.
Dynamic Frequency Control N/A
Channel size 5, 10, 15 and 30 MHz
Maximum power can be controlled lower than the power

Manual Power Control limits shown above in order to control interference to other
users of the band.
Receiver Noise Figure Typically 5 dB
Antenna Type Integrated flat plate antenna
Antenna Gain 18 dBi typical
Antenna Beamwidth 18 Degrees
Max Path Loss (5 MHz

157 dB
channel)
Duplex Scheme Symmetric fixed, asymmetric fixed or adaptive TDD
125 miles (200km) optical Line-of-Sight

Range
6 miles (10km) non-Line-of-Sight
Over-the-Air Encryption Proprietary scrambling mechanism.
Sensitivity at higher modes may be reduced during high

Weather Sensitivity winds through trees due to Adaptive Modulation Threshold
changes.
Error Correction FEC
273
17.2.5 PTP 25600 Emissions and Radio Certifications
Table 38 lists the EMC emissions specifications under which the PTP 25600 has received
type approval. Table 39 lists the radio specifications under which the PTP 25600 has received
type approval.
Table 38 - PTP 25600 EMC Emissions Compliance
Region Specification (Type Approvals)
USA FCC Part 15 (Class B)
Table 39 - PTP 25600 Radio Certifications
USA FCC Part 27
17.2.6 PTP 25600 Available Spectrum Settings
The supported 2.5GHz frequency range is split into three bands, according to the bands
specified in the FCC BRS-EBS Post-Transition Band plan (only for PTP 25600 and Region
Code 16):
• Lower: 2496 MHz to 2572 MHz with a 5.5MHz channel raster (76 MHz total).
• Middle: 2572 MHz to 2614 MHz with a 6 MHz channel raster (42 MHz total).
• Upper: 2618 MHz to 2690 MHz with a 5.5 MHz channel raster (76 MHz total).
NOTE
For the PTP 25600 product variant, the unit will only operate in Fixed Frequency
mode, and the user is unable to select i-DFS.
The PTP 25600 product variant support channel centre frequencies as specified in Table 40.
The 30MHz Channel Bandwidth is not supported in the FCC region.
274
Table 40 - PTP 25600 Channel Plan - FCC BRS-EBS Post-Transition Band
Block Channel Channel Centre Frequencies (MHz)

Bandwidth
(MHz)
Lower 5 2499.25, 2504.75, 2510.25, 2515.75, 2521.25, 2526.75, 2532.25,

Band 2537.75, 2543.25, 2548.75, 2554.25, 2559.75, 2565.25
Segment
10 2502, 2507.5, 2513, 2518.5, 2524, 2529.5, 2535, 2540.5, 2546,
2551.5, 2557, 2562.5
15 2504.75, 2510.25, 2515.75, 2521.25, 2526.75, 2532.25, 2537.75,

2543.25, 2548.75, 2554.25, 2559.75
30 2513, 2524, 2535, 2546
Middle 5 2575, 2581, 2587, 2593, 2599, 2605, 2611

Band
Segment 10 2578, 2584, 2590, 2596, 2602, 2608
15 2581, 2587, 2593, 2599, 2605
30 2587, 2599
Upper 5 2626.75, 2632.25, 2637.75, 2643.25, 2648.75, 2654.25, 2659.75,

Band 2665.25, 2670.75, 2676.25, 2681.75, 2687.25
Segment
10 2629.5, 2635, 2640.5, 2646, 2651.5, 2657, 2662.5, 2668, 2673.5,
2679, 2684.5
15 2632.25, 2637.75, 2643.25, 2648.75, 2654.25, 2659.75, 2665.25,

2670.75, 2676.25, 2681.75
30 2640.5, 2651.5, 2662.5, 2673.5
The channel centre frequencies listed above have been selected to align with the so-called
post-transition BRS channels as shown in Figure 165.
275
NOTE
The PTP 25600 frequency variant supports three portions of the BRS spectrum
allocation. These are configurable at installation and constrain the wireless to operate
in a limited portion of the Spectrum. The three frequency bands are as shown in
Figure 165:
Band 1: channels A, B, C and D (16.5 MHz blocks)
Band 2: channels A through G (6 MHz blocks)
Band 3: channels E, F, G and H (16.5 MHz blocks)
Figure 165 - 2.5 GHz BRS Band Channel Assignments
276
17.2.7 PTP 25600 System Threshold, Output Power and Link Loss
PTP 25600 system threshold, output power and maximum link loss are given in Table 41 (IP
Mode) and Table 42 (TDM Mode). These figures assume that antenna gain is 23 dBi.
Table 41 – PTP 25600 - IP Mode - Threshold, Power and Loss per Modulation Mode
Channel Bandwidth (MHz)
5 10 15 30 All 5 10 15 30
Modulation
Mode MHz MHz MHz MHz Bands MHz MHz MHz MHz
Output
System Threshold (dBm) Power Maximum Link Loss (dB)
(dBm)
BPSK 0.63 single -97.6 -95.1 -93.0 -90.4 +23 156.6 154.1 152.0 149.4
QPSK 0.63 single -93.9 -90.7 -90.5 -86.7 +23 152.9 149.7 146.6 145.7
QPSK 0.87 single -90.7 -87.6 -87.5 -83.9 +23 149.7 146.6 146.5 142.9
16QAM 0.63 single -89.1 -86.0 -86.0 -82.1 +23 148.0 145.5 145.0 140.4
16QAM 0.63 dual -86.7 -83.9 -84.0 -79.4 +23 145.7 142.9 143.0 138.4
16QAM 0.87 single -84.2 -82.5 -80.5 -76.5 +23 143.2 141.4 139.5 135.5
16QAM 0.87 dual -81.0 -77.7 -77.4 -72.9 +23 140.0 136.6 136.4 131.9
64QAM 0.75 single -81.6 -79.2 -77.4 -73.5 +23 140.6 138.2 136.4 132.4
64QAM 0.75 dual -77.8 -74.7 -74.3 -69.8 +23 136.8 133.7 133.3 128.8
64QAM 0.92 single -78.8 -76.3 -74.4 -70.3 +23 137.8 135.2 133.4 129.3
64QAM 0.92 dual -75.5 -71.3 -71.9 -66.5 +23 134.5 130.3 130.9 125.5
256QAM 0.81 single -77.2 -74.9 -72.9 -68.8 +23 136.2 133.9 131.9 127.8
256QAM 0.81 dual -73.5 -70.1 -69.7 -65.1 +23 132.5 129.1 128.7 124.1
277
Table 42 – PTP 25600 - TDM Mode - Threshold, Power and Loss per Modulation Mode
Channel Bandwidth (MHz)
5 10 15 30 All 5 10 15 30
Modulation
MHz MHz MHz MHz Bands MHz MHz MHz MHz
Mode
Output
(dBm)
BPSK 0.63 single -97.6 -95.1 -93.0 -90.4 +23 156.6 154.1 152.0 149.4
QPSK 0.63 single -91.6 -89.1 -88.2 -85.2 +23 150.6 148.1 147.2 144.2
QPSK 0.87 single -88.3 -85.6 -85.1 -81.5 +23 147.3 144.6 144.1 140.5
16QAM 0.63 single -86.4 -83.9 -83.5 -79.4 +23 145.4 142.9 142.5 138.4
16QAM 0.63 dual -84.2 -80.8 -80.7 -76.6 +23 143.2 139.8 139.7 135.6
16QAM 0.87 single -81.7 -78.1 -77.3 -73.6 +23 140.7 137.1 136.3 132.6
16QAM 0.87 dual -78.6 -74.4 -74.3 -70.0 +23 137.6 133.4 133.3 129.0
64QAM 0.75 single -78.8 -75.2 -74.2 -70.6 +23 137.8 134.2 133.2 129.6
64QAM 0.75 dual -75.4 -71.0 -70.9 -66.7 +23 134.4 130.0 129.9 125.7
64QAM 0.92 single -76.0 -73.4 -72.2 -68.6 +23 135.0 132.4 131.2 127.6
64QAM 0.92 dual -73.5 -69.3 -68.9 -64.8 +23 132.5 128.2 127.9 123.8
256QAM 0.81 single -73.4 -71.6 -69.1 -65.4 +23 132.4 130.6 128.1 124.4
256QAM 0.81 dual -70.4 -67.6 -65.9 -61.6 +23 129.4 126.6 124.9 120.6
278

This section contains reference information for the PTP 45600 frequency variant.

Region Examples of Regulatory Limits at 4.5 GHz
Operation of this product is only allowed with a License Key for Region 23 (US
US Federal
Federal).
NTIA Operation of this product is only allowed with a License Key for Region 24.
When shipped, PTP 45600 units are configured with a license key for Region Code 23.

4400 - 4600 5, 10, 15, 20, 30

23 US Federal MHz MHz 27 dBm
4400 - 4600
24 NTIA MHz 10, 20 MHz 27 dBm
279
RF Band 4.400-4.600 GHz
By intelligent Dynamic Frequency Selection (i-DFS) or

Dynamic Frequency Control manual intervention; automatic selection on start-up and
continual adaptation to avoid interference.
Channel size 5, 10, 15, 20 and 30 MHz

users of the band.
Antenna Gain 21.5 dBi typical

157 dB
channel)

Range

changes
280
type approval.
US Federal
US Federal FCC Part 27, NTIA Red Book, TBC
The available spectrum settings for the PTP 45600 are illustrated in this section.
The PTP 45600 product variant does not apply any band edge power reduction.
17.3.5.1 Region Code 23
Adjustment of the lower centre frequency allows the operator to slide the available frequency
settings up and down the 4.5 GHz band in steps of 2 MHz.
In the 30 MHz (Figure 166) and 20 MHz (Figure 167) channel bandwidths, the PTP 45600
variant operates on a 10 MHz channel raster. In the 15 MHz (Figure 168), 10 MHz (Figure
169) and 5 MHz (Figure 170) channel bandwidths, the PTP 45600 variant operates on a 6
MHz channel raster. The channel raster is set to even centre frequencies.
281
Figure 166 – PTP 45600 Available Spectrum in the 30 MHz Channel Bandwidth (RC 23)
282
283
17.3.5.2 Region Code 24 (NTIA)
In the 20 MHz (Figure 171) channel bandwidth, the PTP 45600 variant operates on a 20 MHz
channel raster. In the 10 MHz (Figure 172) channel bandwidth, the PTP 45600 variant
operates on a 10 MHz channel raster. The channel raster is set to even centre frequencies.
284
PTP 45600 system threshold figures are given in Table 48 (IP Mode) and Table 49 (TDM
Mode). These figures assume that antenna gain is 23 dBi.
Table 48 - PTP 45600 - IP Mode - Threshold, Power and Loss per Modulation Mode
Output
(dBm)
Channel
Bandwidth 5 10 15 20 30 All 5 10 15 20 30
Modulation MHz MHz MHz MHz MHz Bands MHz MHz MHz MHz MHz
Mode
BPSK 0.63 single -96.6 -93.7 -92.0 -90.4 -88.0 +27 166.6 163.7 162.0 160.4 158.0
QPSK 0.63 single -92.0 -91.4 -89.3 -88.5 -85.8 +27 160.5 159.9 159.3 158.5 155.8
QPSK 0.87 single -90.0 -87.6 -85.7 -84.9 -82.2 +27 160.0 157.6 155.7 154.9 152.2
16QAM 0.63 single -88.3 -85.5 -83.3 -82.5 -80.1 +27 158.3 155.5 153.3 152.5 150.1
16QAM 0.63 dual -85.5 -81.9 -79.5 -78.9 -77.1 +27 155.5 151.9 149.5 148.9 147.1
16QAM 0.87 single -84.6 -80.7 -78.6 -77.8 -75.5 +27 154.6 150.7 148.6 147.8 145.5
16QAM 0.87 dual -81.3 -77.3 -75.0 -74.3 -72.3 +27 151.3 147.3 145.0 144.3 142.3
64QAM 0.75 single -81.2 -77.6 -75.5 -74.7 -72.4 +25 149.2 145.6 143.5 142.7 140.4
64QAM 0.75 dual -78.2 -74.2 -71.8 -71.1 -69.3 +25 146.2 142.2 139.8 139.1 137.3
64QAM 0.92 single -76.8 -73.1 -71.3 -70.0 -67.7 +25 144.8 141.1 139.3 138.0 135.7
64QAM 0.92 dual -73.2 -69.4 -67.6 -66.9 -65.0 +25 141.2 137.4 135.6 134.9 133.0
256QAM 0.81 single

Not available
256QAM 0.81 dual
285
Table 49 - PTP 45600 - TDM Mode - Threshold, Power and Loss per Modulation Mode
Output
(dBm)
Channel
Bandwidth 5 10 15 20 30 All 5 10 15 20 30
Modulation MHz MHz MHz MHz MHz Bands MHz MHz MHz MHz MHz
Mode
BPSK 0.63 single -96.6 -93.7 -92.0 -90.4 -88.0 +27 166.6 163.7 162.0 160.4 158.0
QPSK 0.63 single -90.4 -89.1 -87.8 -86.0 -83.1 +27 158.1 155.4 153.3 151.6 149.5
QPSK 0.87 single -88.1 -85.4 -83.3 -81.6 -79.5 +27 160.3 159.1 157.8 156.0 153.1
16QAM 0.63 single -86.1 -82.8 -80.7 -79.2 -77.2 +27 156.1 152.8 150.7 149.2 147.2
16QAM 0.63 dual -82.5 -79.1 -77.2 -75.6 -73.9 +27 152.5 149.1 147.2 145.6 143.9
16QAM 0.87 single -81.2 -78.2 -76.1 -74.4 -72.0 +27 151.2 148.2 146.1 144.4 142.0
16QAM 0.87 dual -77.7 -74.4 -72.4 -70.8 -69.2 +27 147.7 144.4 142.4 140.8 139.2
64QAM 0.75 single -77.7 -74.5 -72.4 -70.7 -68.6 +25 145.7 142.5 140.4 138.7 136.6
64QAM 0.75 dual -74.2 -70.9 -69.1 -67.5 -65.9 +25 142.2 138.9 137.1 135.5 133.9
64QAM 0.92 single -75.9 -72.2 -70.2 -68.6 -66.5 +25 143.9 140.2 138.2 136.6 134.5
64QAM 0.92 dual -71.7 -68.5 -66.8 -65.4 -63.7 +25 139.7 136.5 134.8 133.4 131.7
256QAM 0.81 single

Not available
256QAM 0.81 dual
286


Operation of this product is only allowed with a License Key for Regions 15 or 23
US Federal
(US Federal).
NTIA Operation of this product is only allowed with a License Key for Region 24.
alternative license key is provided in the Deployment Guide for Region Code 23. If the link is
to be installed in any other permitted region, the user must obtain a new license key from the
reseller or distributor.

USA/Canada 4940 - 4990 See note

14 Public Safety MHz 5, 10, 20 MHz 24 dBm below.
US Federal 4710 - 5000 5, 10, 15, 20
15 Extended MHz MHz 27 dBm
4710 - 4940 5, 10, 15, 20
23 US Federal MHz MHz 27 dBm
4700 - 4940
24 NTIA MHz 10, 20 MHz 27 dBm
287
NOTE
Region Code 14 Max Power depends upon Antenna Gain:
If Antenna Gain < 26 dBi then Max Power = 24 dBm
If Antenna Gain >= 26 dBi then Max Power = (50 – Antenna Gain) dBm
RF Band 4.710-5.000 GHz

Channel size 5, 10, 15, and 20 MHz

users of the band.

157 dB
channel)

Range
288

changes
type approval.
US Federal
US Federal FCC Part 27, NTIA Red Book, TBC
289
17.4.5.1 Region Codes 15 and 23
channel raster. In the 15 MHz (Figure 174), 10 MHz (Figure 175) and 5 MHz (Figure 176)
channel bandwidths, the PTP 48600 variant operates on a 5 MHz channel raster. The
channel raster is set to even centre frequencies.
Figure 173 – PTP 48600 Available Spectrum in the 20 MHz Channel Bandwidth (RC 15 and 23)
290
291
17.4.5.2 Region Code 24 (NTIA)
channel raster. In the 10 MHz (Figure 178) channel bandwidth, the PTP 48600 variant
operates on a 10 MHz channel raster. The channel raster is set to even centre frequencies.
292
Output Power
System Threshold (dBm) Maximum Link Loss (dB)
(dBm)
Channel Bandwidth 5 10 15 20 5, 10, 15 20 5 10 15 20

MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz
Modulation Mode
BPSK 0.63 single -98.6 -95.5 -93.3 -91.9 +27 +27 169.6 166.5 164.3 162.9
QPSK 0.63 single -94.3 -90.7 -89.6 -87.5 +27 +27 165.3 161.7 160.6 158.5
QPSK 0.87 single -90.8 -87.3 -85.9 -84.0 +27 +26 161.8 158.3 156.9 154.0
16QAM 0.63 single -88.7 -85.2 -83.6 -81.8 +25 +25 157.7 154.2 152.6 150.8
16QAM 0.63 dual -85.3 -81.6 -80.0 -78.5 +25 +25 154.3 150.6 149.0 147.5
16QAM 0.87 single -84.4 -80.6 -78.8 -77.3 +25 +25 153.4 149.6 147.8 146.3
16QAM 0.87 dual -81.0 -77.2 -75.9 -74.5 +25 +25 150.0 146.2 144.9 143.5
64QAM 0.75 single -81.2 -77.7 -76.1 -74.7 +23 +23 148.2 144.7 143.1 141.7
64QAM 0.75 dual -78.2 -74.7 -73.4 -71.9 +23 +23 145.2 141.7 140.4 138.9
64QAM 0.92 single -77.0 -73.9 -72.7 -71.0 +21 +21 142.0 138.9 137.7 136.0
64QAM 0.92 dual -74.0 -70.9 -69.7 -67.6 +21 +21 139.0 135.9 134.7 132.6
256QAM 0.81 single -75.2 -71.9 -70.1 -68.0 +20 +20 139.2 135.9 134.1 132.0
256QAM 0.81 dual -72.1 -68.4 -66.9 -64.5 +20 +20 136.1 132.4 130.9 128.5
293
Output Power
System Threshold (dBm) Maximum Link Loss (dB)
(dBm)
Channel Bandwidth 5 10 15 20 5, 10, 15 20 5 10 15 20

MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz
Modulation Mode
BPSK 0.63 single -98.6 -95.5 -93.3 -91.9 +27 +27 169.6 166.5 164.3 162.9
QPSK 0.63 single -91.4 -88.8 -87.8 -85.7 +27 +27 162.4 159.8 158.8 156.7
QPSK 0.87 single -87.9 -85.2 -83.5 -81.9 +27 +26 158.9 156.2 154.5 151.9
16QAM 0.63 single -85.4 -82.7 -81.1 -79.6 +25 +25 154.4 151.7 150.1 148.6
16QAM 0.63 dual -81.9 -79.5 -77.8 -76.5 +25 +25 150.9 148.5 146.8 145.5
16QAM 0.87 single -81.0 -78.2 -76.8 -75.5 +25 +25 150.0 147.2 145.8 144.5
16QAM 0.87 dual -77.8 -75.4 -74.0 -72.5 +25 +25 146.8 144.4 143.0 141.5
64QAM 0.75 single -77.9 -75.2 -73.9 -72.6 +23 +23 144.9 142.2 140.9 139.6
64QAM 0.75 dual -75.0 -72.6 -71.1 -69.3 +23 +23 142.0 139.6 138.1 136.3
64QAM 0.92 single -76.5 -73.9 -72.3 -70.7 +21 +21 141.5 138.9 137.3 135.7
64QAM 0.92 dual -73.3 -71.0 -69.0 -67.2 +21 +21 138.3 136.0 134.0 132.2
256QAM 0.81 single -75.1 -72.3 -70.8 -69.3 +20 +20 139.1 136.3 134.8 133.3
256QAM 0.81 dual -71.7 -69.3 -67.3 -65.4 +20 +20 135.7 133.3 131.3 129.4
294


USA, Canada Operation of this product is only allowed with a License Key for Region 14
and Hong Kong (USA/Canada Public Safety) or Region 18 (Hong Kong Public Safety).
Public Safety
alternative license key is provided in the Deployment Guide for Region Code 18.

USA/Canada 4940 - 4990 See note

Hong Kong 4900 - 4950 See note
NOTE
Region Codes 14 and 18 Max Power depends upon Antenna Gain:
If Antenna Gain < 26 dBi then Max Power = 24 dBm
If Antenna Gain >= 26 dBi then Max Power = (50 – Antenna Gain) dBm
295
The PTP 49600 complies with the regulations that are in force in the USA and Canada. The
relevant notifications are specified in this section.
17.5.3.1 PTP 49600 FCC and IC Notification
The system has been approved under FCC Part 90 and Industry Canada RSS-111 for Public
Safety Agency usage. The installer or operator is responsible for obtaining the appropriate
site licenses before installing or using the system.
FCC IDs and Industry Canada Certification Numbers are listed below:
RF Band 4.900-4.990 GHz

Channel size 5, 10 and 20 MHz

users of the band.
296
Typical: 22 dBi
Antenna Gain
Maximum permitted: 26 dBi

157 dB
channel)

Range

changes
type approval.
USA FCC Part 15B
USA FCC Part 90
Canada RSS-111
297
The available spectrum settings for the PTP 49600 are illustrated in this section. In the 20
MHz (Figure 179), 10 MHz (Figure 180) and 5 MHz (Figure 181) channel bandwidths, the
PTP 49600 variant operates on a 5 MHz channel raster. The channel raster is set to even
centre frequencies.
NOTE
These tables contain data for one typical Region Code. The specified channel centre
frequencies may not be available in other Region Codes.
Figure 179 – PTP 49600 Available Spectrum in the 20 MHz Channel Bandwidth
298
System Threshold Output Maximum Link Loss

(dBm) Power (dB)
(dBm)
Channel 20
Bandwidth 5 10 20 All 5 10
MHz
Modulation MHz MHz MHz Bands MHz MHz
Mode
BPSK 0.63 single -98.6 -95.5 -91.9 +24 166.6 163.5 159.9
QPSK 0.63 single -94.3 -90.7 -87.5 +24 162.3 158.7 155.5
QPSK 0.87 single -90.8 -87.3 -84.0 +24 158.8 155.3 152.0
16QAM 0.63 single -88.7 -85.2 -81.8 +24 156.7 153.2 149.8
16QAM 0.63 dual -85.3 -81.6 -78.5 +24 153.3 149.6 146.5
16QAM 0.87 single -84.4 -80.6 -77.3 +24 152.4 148.6 145.3
16QAM 0.87 dual -81.0 -77.2 -74.5 +24 149.0 145.2 142.5
64QAM 0.75 single -81.2 -77.7 -74.7 +23 148.2 144.7 141.7
64QAM 0.75 dual -78.2 -74.7 -71.9 +23 145.2 141.7 138.9
64QAM 0.92 single -77.0 -73.9 -71.0 +21 142.0 138.9 136.0
64QAM 0.92 dual -74.0 -70.9 -67.6 +21 139.0 135.9 132.6
256QAM 0.81 single -75.2 -71.9 -68.0 +20 139.2 135.9 132.0
256QAM 0.81 dual -72.1 -68.4 -64.5 +20 136.1 132.4 128.5
299
System Threshold Output Maximum Link Loss

(dBm) Power (dB)
(dBm)
Channel 20
Bandwidth 5 10 20 All 5 10
MHz
Modulation MHz MHz MHz Bands MHz MHz
Mode
BPSK 0.63 single -98.6 -95.5 -91.9 +24 166.6 163.5 159.9
QPSK 0.63 single -91.4 -88.8 -85.7 +24 159.4 156.8 153.7
QPSK 0.87 single -87.9 -85.2 -81.9 +24 155.9 153.2 149.9
16QAM 0.63 single -85.4 -82.7 -79.6 +24 153.4 150.7 147.6
16QAM 0.63 dual -81.9 -79.5 -76.5 +24 149.9 147.5 144.5
16QAM 0.87 single -81.0 -78.2 -75.5 +24 149.0 146.2 143.5
16QAM 0.87 dual -77.8 -75.4 -72.5 +24 145.8 143.4 140.5
64QAM 0.75 single -77.9 -75.2 -72.6 +23 144.9 142.2 139.6
64QAM 0.75 dual -75.0 -72.6 -69.3 +23 142.0 139.6 136.3
64QAM 0.92 single -76.5 -73.9 -70.7 +21 141.5 138.9 135.7
64QAM 0.92 dual -73.3 -71.0 -67.2 +21 138.3 136.0 132.2
256QAM 0.81 single -75.1 -72.3 -69.3 +20 139.1 136.3 133.3
256QAM 0.81 dual -71.7 -69.3 -65.4 +20 135.7 133.3 129.4
300


Operation of this product is only allowed with a License Key for Region 12. This
implements Radar Detection in accordance with FCC Regulations and limits the
FCC EIRP to the regulatory limits below:
EIRP ≤ Max of [(17 +10 x Log(Channel BW)) and 30] dBm.
implements Radar Detection, including barring of the band from 5600 MHz to
ETSI 5650 MHz and limits the EIRP to the regulatory limits below:
EIRP ≤ Max of [(17 +10 x Log(Channel BW)) and 30] dBm
Australia, implements Radar Detection, including barring of the band from 5600 MHz to
Canada 5650 MHz and limits the EIRP to the regulatory limits below:
Operation of this product is only allowed with a License Key for Region 20 (30
Thailand
dBm or 1W EIRP)
Operation of this product is only allowed with a License Key for Region 21 (28
Korea
dBm EIRP (15 MHz), 27 dBm EIRP (10 MHz), 24 dBm EIRP (5 MHz)).
General Notice Applicable to Europe – 5.4 GHz

This equipment complies with the essential requirements for the
EU R&E Directive 1999/5/EC.
301
NOTE
In regions other than EU/USA, specific local regulations may apply. It is the
responsibility of the installer/user to check that the equipment as deployed meets
local regulatory requirements.
PTP 54600 units may be operated in any of the regions listed in Table 65. When shipped,
PTP 54600 units are configured with a license key for Region Code 26. Alternative license
keys are provided in the Deployment Guide for Region Codes 12 and 13. If the link is to be
installed in any other permitted region, the user must obtain a new license key from the
reseller or distributor.

7 Full Power + 5470 - 5725 Yes 5, 10, 15, 30 25 dBm
Radar MHz MHz
8 Full Power 5470 - 5725 5, 10, 15, 30 25 dBm
MHz MHz
12 FCC 5470 - 5725 Yes 30 MHz 30 dBm EIRP
MHz
15 MHz 27 dBm EIRP
10 MHz 25 dBm EIRP
5 MHz 22 dBm EIRP
13 Australia, 5470 - 5600 Yes 30 MHz 30 dBm EIRP The band 5600
Canada MHz MHz to 5650
5650 - 5725 15 MHz 27 dBm EIRP MHz is reserved
MHz 10 MHz 25 dBm EIRP for the use of
weather radars.
5 MHz 22 dBm EIRP
20 Thailand 5470 - 5725 5, 10, 15, 30 30 dBm EIRP

MHz MHz
21 Korea 5470 - 5650 15 MHz 28 dBm EIRP
MHz
10 MHz 27 dBm EIRP
5 MHz 24 dBm EIRP
302

26 ETSI 5470 - 5600 Yes 30 MHz 30 dBm EIRP The band 5600
MHz MHz to 5650
5650 - 5725 MHz is reserved
MHz 15 MHz 27 dBm EIRP for the use of
weather radars.
10 MHz 25 dBm EIRP
5 MHz 22 dBm EIRP
The PTP 54600 complies with the regulations that are in force in the USA, Canada and
Europe. The relevant notifications are specified in this section.
U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification.
This device complies with part 15.407 of the US FCC Rules and Regulations and with RSS-
210 Issue 7 of Industry Canada. Operation is subject to the following two conditions: (1) This
device may not cause harmful interference, and (2) This device must accept any interference
received, including interference that may cause undesired operation. In Canada, users should
be cautioned to take note that high power radars are allocated as primary users (meaning
they have priority) of 5250 – 5350 MHz and 5650 – 5850 MHz and these radars could cause
interference and/or damage to license-exempt local area networks (LELAN).
For the connectorized version of the product and in order to reduce potential radio
interference to other users, the antenna type and its gain should be so chosen that the
equivalent isotropically radiated power (EIRP) is not more than that permitted by the
regulations. The transmitted power must be reduced to achieve this requirement.
303
device, pursuant to Part 15 of the US FCC Rules and with RSS-210 of Industry Canada.
These limits are designed to provide reasonable protection against harmful interference in a
residential installation. This equipment generates, uses, and can radiate radio-frequency
energy and, if not installed and used in accordance with these instructions, may cause
harmful interference to radio communications. If this equipment does cause harmful
interference to radio or television reception, which can be determined by turning the
equipment on and off, the user is encouraged to correct the interference by one or more of
the following measures:
• FCC IDs and Industry Canada Certification Numbers are listed below:
17.6.3.2 PTP 54600 European Union Notification
The PTP 54600 product is a two-way radio transceiver suitable for use in Broadband Wireless
Access System (WAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA)
systems. It is a Class 1 device and uses operating frequencies that are harmonized
throughout the EU member states. The operator is responsible for obtaining any national
licenses required to operate this product and these must be obtained before using the product
in any particular country.
Hereby, Motorola declares that the PTP 54600 product complies with the essential
requirements and other relevant provisions of Directive 1999/5/EC. The declaration of
conformity may be consulted at http://motorola.canopywireless.com/doc.php.
304
This equipment is marked to show compliance with the European R&TTE directive
1999/5/EC.
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive
The European Union's WEEE directive requires that products sold into EU countries must
have the crossed out trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and
end-users in EU countries should not dispose of electronic and electrical equipment or
accessories in household waste. Customers or end-users in EU countries should contact their
local equipment supplier representative or service center for information about the waste
collection system in their country.
RF Band 5.470-5.725 GHz
By dynamic frequency control and manual intervention

Channel Selection Automatic detection on start-up and continual adaptation to
avoid interference.
Initial capture 10-15 sec. Out of service on interference 100

Dynamic Frequency Control
ms.

users of the band.
305
Typical: 23 dBi
Maximum permitted at channel bandwidth 30, 15 or 10
Antenna Gain
MHz: 34.9 dBi
Maximum permitted at channel bandwidth 5 MHz: 33.4dBi

169 dB
channel)

Range

changes
306
type approval.
USA FCC Part 15 Class B
Canada CSA Std C108.8, 1993 Class B
Europe EN55022 CISPR 22
USA FCC Part 15 E
Canada RSS 210 Issue 7, Annex 9
EN301 893 V1.4.1 with DFS testing using radar parameters as

Europe
defined in V1.5.1
307
In the 30 MHz channel bandwidth (Figure 182), the PTP 54600 variant operates on a 10 MHz
channel raster is set to even centre frequencies. The PTP 54600 product variant does not
apply any band edge power reduction
NOTE
308
309
PTP 54600 system threshold, output power and maximum link loss are given in Table 69 (IP
Mode) and Table 70 (TDM Mode). These figures assume that antenna gain is 23 dBi.
Table 69 – PTP 54600 - IP Mode - Threshold, Power and Loss per Modulation Mode
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Modulation MHz MHz MHz MHz Bands MHz MHz MHz
Mode
BPSK 0.63 single -98.2 -94.6 -92.3 -88.9 +25 169.2 165.6 163.3 159.9
QPSK 0.63 single -93.0 -90.0 -88.5 -82.9 +24 163.0 160.0 158.5 152.9
QPSK 0.87 single -90.2 -86.7 -85.3 -80.1 +23 159.2 155.7 154.3 149.1
16QAM 0.63 single -88.0 -83.8 -82.8 -78.3 +22 156.0 151.8 150.8 146.3
16QAM 0.63 dual -84.3 -80.7 -79.3 -74.6 +22 152.3 148.7 147.3 142.6
16QAM 0.87 single -82.4 -79.1 -78.2 -73.0 +20 148.4 145.1 144.2 139.0
16QAM 0.87 dual -79.7 -75.7 -74.7 -70.6 +20 145.7 141.7 140.7 136.6
64QAM 0.75 single -78.9 -76.4 -74.9 -70.3 +18 142.9 140.4 138.9 134.3
64QAM 0.75 dual -76.5 -72.7 -71.6 -67.7 +18 140.5 136.7 135.6 131.7
64QAM 0.92 single -74.4 -71.7 -70.4 -65.0 +18 138.4 135.7 134.4 129.0
64 QAM 0.92 dual -70.7 -68.5 -66.9 -62.3 +18 134.7 132.5 130.9 126.3
256QAM 0.81 single N/A N/A N/A -63.6 +18 N/A N/A N/A 127.6
256QAM 0.81 dual N/A N/A N/A -60.5 +18 N/A N/A N/A 124.5
310
Table 70 – PTP 54600 - TDM Mode - Threshold, Power and Loss per Modulation Mode
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Mode
BPSK 0.63 single -98.2 -94.6 -92.3 -88.9 +25 169.2 165.6 163.3 159.9
QPSK 0.63 single -89.7 -88.3 -86.4 -81.4 +24 159.7 158.3 156.4 151.4
QPSK 0.87 single -86.7 -84.3 -82.3 -78.4 +23 155.6 153.3 151.3 147.4
16QAM 0.63 single -86.6 -81.8 -79.9 -76.0 +22 151.7 149.8 147.9 144.0
16QAM 0.63 dual -83.7 -78.2 -76.5 -72.4 +22 148.8 146.3 144.5 140.4
16QAM 0.87 single -78.8 -76.6 -75.5 -69.8 +20 144.8 142.6 141.5 135.8
16QAM 0.87 dual -76.9 -73.9 -72.2 -68.7 +20 142.9 139.9 138.2 134.7
64QAM 0.75 single -74.7 -72.2 -71.8 -66.6 +18 138.7 136.2 135.8 130.6
64QAM 0.75 dual -73.0 -70.4 -68.8 -65.6 +18 137.0 134.4 132.8 129.6
64QAM 0.92 single -70.9 -68.6 -67.4 -62.9 +18 134.9 132.6 131.4 126.9
64 QAM 0.92 dual -68.2 -65.6 -64.2 -60.5 +18 132.1 129.6 128.2 124.5
311
17.6.8 PTP 54600 FCC Antenna Restrictions
In FCC regions, external antennas from the list in Table 71 can be used with the
Connectorized version of the PTP 54600. These are approved by the FCC for use with the
product and are constrained by the following limit for Single/Dual Polarization Parabolic Dish
Antennas: up to 34.9 dBi (33.4 dBi for 5 MHz bandwidth) per polarization or antenna.
However, the Maximum Transmit Power must be reduced to avoid exceeding the EIRP limits.
In FCC regions when using external antennas, cable loss between the connectorized version
of the PTP 600 Series Bridge and the antenna ports must not be less than 1.2 dB.
CAUTION
Antennas not included in this table, or those having a gain greater than the specified
maximum, are strictly prohibited for use with the PTP 54600. The required antenna
impedance is 50 ohms.
Table 71 - Allowed Antennas for Deployment in USA/Canada – 5.4 GHz

Gain Parabolic
Manufacturer Antenna Type
(dBi) Dish
Andrew Andrew 2-foot Parabolic, P2F-52 (29.4dBi) 29.4 Y
Andrew Andrew 2-foot Dual-Pol Parabolic, PX2F-52 29.4 Y
(29.4dBi)
(33.4dBi)
(34.9dBi)
Gabriel Gabriel 2-foot High Performance QuickFire 28.2 Y
Parabolic, HQF2-52-N
Gabriel Gabriel 4-foot High Performance QuickFire 34.4 Y
Parabolic, HQF4-52-N
Gabriel Gabriel 2-foot High Performance Dual 28.1 Y
QuickFire Parabolic, HQFD2-52-N
312
Gain Parabolic
(dBi) Dish
Gabriel Gabriel 2-foot Standard QuickFire 28.5 Y
Parabolic,
QF2-52-N
Parabolic,
QF2-52-N-RK
Gabriel Gabriel 2.5-foot Standard QuickFire 31.2 Y
Parabolic, QF2.5-52-N
Parabolic,
QF4-52-N
Parabolic,
QF4-52-N-RK
Gabriel Gabriel 2-foot Standard Dual QuickFire 28.4 Y
Parabolic, QFD2-52-N
Gabriel Gabriel 2.5-foot Standard Dual QuickFire 31.1 Y
Parabolic, QFD2.5-52-N
Parabolic, QFD2-52-N-RK
RadioWaves Radio Waves 2-foot Dual-Pol Parabolic, 28.1 Y
SPD2-5.2 (28.1dBi)
RadioWaves Radio Waves 2-foot Parabolic, SP2-5.2 29 Y
(29.0dBi)
SPD3-5.2 (31.1dBi)
RadioWaves Radio Waves 3-foot Parabolic, SP3-5.2 31.4 Y
(31.4dBi)
SPD4-5.2 (34.4dBi)
(34.8dBi)
RadioWaves Radio Waves 2-foot Parabolic, SP2-2/5 28.3 Y
(28.3dBi)
(31.4dBi)
313
Gain Parabolic
(dBi) Dish
(34.6dBi)
RFS RFS 2-foot Parabolic, SPF2-52AN or 27.9 Y
SPFX2-52AN (27.9dBi)
SPFX3-52AN(31.4dBi)
SPFX4-52AN(33.9dBi)
RFS RFS 2-foot HP Parabolic, SDF2-52AN or 31.4 Y
SDFX2-52AN (31.4dBi)
RFS RFS 4-foot HP Parabolic, SDF4-52AN or 33.9 Y
SDFX4-52AN (33.9dBi)
314

variant.

USA/ Equipment can be operated in any mode, best results will be obtained
Canada/ using Region 1 settings. There are some limitations on the use of
Taiwan/ Brazil antennas above 4ft diameter plus a band edge power reduction.
Operation of this product is only allowed with a License Key for Region
China
2 (33 dBm or 2W EIRP).
Australia
Hong Kong
Operation of this product is allowed with a License Key for Region 4.
This implements Radar Detection with barring of the band from 5795
UK MHz to 5815 MHz and above 5850 MHz. It limits the EIRP to the
Regulatory Limits below:
Singapore
5 (20 dBm or 100mW EIRP).
Eire 6 (33 dBm or 2W EIRP). The lower power limits are lower in narrower
bandwidths.
Korea
India 19 (36 dBm or 4W EIRP at 15 MHz and 10 MHz and 33 dBm or 2 W
EIRP at 5 MHz channel bandwidth).
Thailand
315

Germany Operation of this product is only allowed with a License Key for Region
22. This limits the band of operation to 5755 MHz to 5850 MHz and
limits the EIRP to the Regulatory Limits below:
Bahrain Operation of this product is allowed with a License Key for Region 24 .
This limits the EIRP to the Regulatory Limits below:
Norway Under Norway Regulations, operation of this product is only allowed
with a License Key for Region 7. This implements Radar Detection and
limits the EIRP to the Regulatory Limits below:
Spectral density at border between Norway and neighboring countries
shall not exceed -122,5 dBW/m2 measured with a reference
bandwidth of 1 MHz.
General Notice Applicable to Europe – 5.8 GHz

This equipment complies with the essential requirements for the EU R&E Directive
1999/5/EC.
The use of 5.8GHz for Point to Point radio links is not harmonized across the EU and
currently the product may only be deployed in the UK, Eire (IRL), Germany, Denmark
and Norway.
However, the regulatory situation in Europe is changing and the radio spectrum may
become available in other countries in the near future. Please contact Motorola for the
latest situation.
316
PTP 58600 units are configured with a license key for Region Code 1. An alternative license
key is provided in the Deployment Guide for Region Code 25. For any other permitted region,
obtain a new license key from the reseller or distributor.

Region License / Frequencies DFS Channel Max Power Notes
Code Regulation Bandwidth
1 FCC USA, 5725 - 5850 5, 10, 15, 30 25 dBm Reduced TX
Canada, MHz MHz power at band
Taiwan, edges
Brazil
2 China 5725 - 5850 30 MHz 33 dBm EIRP
MHz
15 MHz 31 dBm EIRP
10 MHz 30 dBm EIRP
5 MHz 27 dBm EIRP
3 Australia, 5725 - 5850 5, 10, 15, 30 36 dBm EIRP
Hong Kong MHz MHz
4 UK 5725 - 5795 Yes 30 MHz 35 dBm EIRP 5795 MHz to
MHz 5815 MHz is
5815 - 5850 15 MHz 34 dBm EIRP assigned for
MHz Road Transport
10 MHz 32 dBm EIRP and Traffic
Telematics
5 MHz 29 dBm EIRP (RTTT).
5 Singapore 5725 - 5850 5, 10, 15, 30 20 dBm EIRP

MHz MHz
6 Eire 5725 - 5850 30 MHz 33 dBm EIRP
MHz
15 MHz 31 dBm EIRP
10 MHz 30 dBm EIRP
5 MHz 27 dBm EIRP
7 Norway 5725 - 5795 Yes 30 MHz 53 dBm EIRP 5795 MHz to
MHz 5815 MHz is
15 MHz 51 dBm EIRP
5815 - 5850 assigned for
MHz 10 MHz 50 dBm EIRP Road Transport
and Traffic
5 MHz 47 dBm EIRP Telematics
(RTTT).
317
Region License / Frequencies DFS Channel Max Power Notes

Code Regulation Bandwidth
8 Full Power 5725 - 5850 5, 10, 15, 30 25 dBm
MHz MHz
11 Korea 5725 - 5825 30 MHz 43 dBm EIRP
MHz
15 MHz 41 dBm EIRP
10 MHz 40 dBm EIRP
5 MHz 37 dBm EIRP
19 India 5825 - 5850 10, 15 MHz 36 dBm EIRP

MHz
5 MHz 33 dBm EIRP
20 Thailand 5725 - 5850 5, 10, 15, 30 30 dBm EIRP

MHz MHz
22 Germany 5755 - 5850 Yes 30 MHz 35 dBm EIRP 1dB reduction
MHz required in 30
15 MHz 34 dBm EIRP MHz to achieve
10 MHz 32 dBm EIRP adjacent
channel
5 MHz 29 dBm EIRP emissions
24 Bahrain 5725 - 5850 Yes 30 MHz 33 dBm EIRP
MHz
15 MHz 31 dBm EIRP
10 MHz 30 dBm EIRP
5 MHz 27 dBm EIRP
25 ETSI 5725 - 5850 Yes 30 MHz 35 dBm EIRP 1dB reduction
MHz required in 30
15 MHz 34 dBm EIRP
MHz to achieve
10 MHz 32 dBm EIRP adjacent
channel
5 MHz 29 dBm EIRP emissions
27 Denmark 5725 - 5795 Yes 30 MHz 35 dBm EIRP 5795 MHz to
5815 - 5850 5815 MHz is
MHz 15 MHz 34 dBm EIRP assigned for
10 MHz 32 dBm EIRP Road Transport
and Traffic
5 MHz 29 dBm EIRP Telematics
(RTTT)
318
The PTP 58600 complies with the regulations that are in force in the USA, Canada and
Europe. The relevant notifications are specified in this section.
U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification.
This system has achieved Type Approval in various countries around the world. This means
that the system has been tested against various local technical regulations and found to
comply. The frequency band in which the system operates is ‘license exempt’ and the system
is allowed to be used provided it does not cause interference. Further, the licensing authority
does not guaranteed protection against interference from other products and installations.
This device complies with part 15 of the US FCC Rules and Regulations and with RSS-210 of
Industry Canada. Operation is subject to the following two conditions: (1) This device may
not cause harmful interference, and (2) This device must accept any interference received,
including interference that may cause undesired operation. In Canada, users should be
cautioned to take note that high power radars are allocated as primary users (meaning they
have priority) of the 5650 – 5850 MHz spectrum and these radars could cause interference
and/or damage to license-exempt local area networks (LELAN).
For the connectorized version of the product and in order to reduce potential radio
interference to other users, the antenna type and its gain should be so chosen that the
Effective Isotropically Radiated Power (EIRP) is not more than that permitted for successful
communication.
device, pursuant to Part 15 of the US FCC Rules and with RSS-210 of Industry Canada.
These limits are designed to provide reasonable protection against harmful interference in a
residential installation. This equipment generates, uses, and can radiate radio-frequency
energy and, if not installed and used in accordance with these instructions, may cause
harmful interference to radio communications. If this equipment does cause harmful
interference to radio or television reception, which can be determined by turning the
equipment on and off, the user is encouraged to correct the interference by one or more of
the following measures:
319
FCC IDs and Industry Canada Certification Numbers are listed below:
17.7.3.2 PTP 58600 European Union Notification
The PTP 58600 is a Class 2 device as it operates on frequencies that are not
harmonized across the EU. Currently the product may only be operated in the UK, Eire (IRL),
Germany, Norway and Denmark. However, the regulatory situation in Europe is changing
and the radio spectrum may become available in other countries in future. See www.ero.dk
for further information. The operator is responsible for obtaining any national licenses
required to operate this product and these must be obtained before using the product in any
particular country.
Hereby, Motorola declares that the PTP 58600 product complies with the essential
requirements and other relevant provisions of Directive 1999/5/EC. The declaration of
conformity may be consulted at http://motorola.canopywireless.com/doc.php.
This equipment is marked to show compliance with the European R&TTE directive 1999/5/EC.
320
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive
The European Union's WEEE directive requires that products sold into EU countries must
have the crossed out trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and
end-users in EU countries should not dispose of electronic and electrical equipment or
accessories in household waste. Customers or end-users in EU countries should contact their
local equipment supplier representative or service center for information about the waste
collection system in their country.
17.7.3.3 UK Notification
The PTP 58600 connectorized product has been notified for operation in the UK, and when
operated in accordance with instructions for use it is compliant with UK Interface Requirement
IR2007. For UK use, installations must conform to the requirements of IR2007 in terms of
EIRP spectral density against elevation profile above the local horizon in order to protect
Fixed Satellite Services. The frequency range 5795-5815 MHz is assigned to Road Transport
& Traffic Telematics (RTTT) in the U.K. and shall not be used by FWA systems in order to
protect RTTT devices. UK Interface Requirement IR2007 specifies that radiolocation services
shall be protected by a Dynamic Frequency Selection (DFS) mechanism to prevent co-
channel operation in the presence of radar signals.
CAUTION
This equipment operates as a secondary application, so it has no rights against
harmful interference, even if generated by similar equipment, and must not cause
harmful interference on systems operating as primary applications.
321
RF Band 5.725-5.850 GHz

avoid interference.

ms.

users of the band.
Typical: 23 dBi
Antenna Gain
Maximum permitted: 37.7 dBi

166 dB
Channel)
125 miles (200km) optical line-of-sight

Range
6 miles (10km) non-line-of-sight

changes
322
type approval.
USA
FCC Part 15 Class B
Canada
CSA Std C108.8, 1993 Class B
Europe
EN55022 CISPR 22
USA FCC Part 15.247
CANADA RSS 210 Issue 7, Annex 8
UK IR 2007
Eire ComReg 02/71R1
EU EN302 502 v 1.2.1
323
NOTE
324
325
17.7.6.1 PTP 58600 Transmit Power Reduction at the Band Edges
Operation at or near the 5.8 GHz band edges can results in a lower maximum transmit power.
In some configurations the PTP 600 Series Bridge solution reduces the power when
operating at the edge channels. The amount of reduction, if any, is dependant on the region
code of the region of operation. This currently only affects systems configured with Region
Code 1. The power reductions in the edge channels for 5 MHz, 10 MHz, 15 MHz and 30 MHz
are presented in Table 77 (for region code 1 ONLY).
Table 77 – PTP 58600 Band Edge Tx Power Reduction

Power Levels for Channel Width (MHz)
Channel Centre
5 10 15 30
5730 25 N/A N/A N/A
5732 25 23 N/A N/A
5734 25 25 N/A N/A
5736 25 25 23 N/A
5738 25 25 25 N/A
5740 25 25 25 17
5742 - 5750 25 25 25 21
5752 - 5822 25 25 25 25
5824 - 5832 25 25 25 21
5834 25 25 25 17
5840 25 25 23 N/A
5842 25 23 19 N/A
5844 25 19 N/A N/A
5846 23 N/A N/A N/A
326
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Mode
BPSK 0.63 single -95.1 -92.5 -90.8 -86.3 +25 166.1 163.5 161.8 157.3
QPSK 0.63 single -91.9 -90.0 -87.7 -83.0 +24 161.9 160.0 157.7 153.0
QPSK 0.87 single -88.7 -86.6 -84.8 -80.3 +23 157.7 155.6 153.8 149.3
16QAM 0.63 single -86.0 -84.3 -82.4 -78.3 +22 154.0 152.3 150.4 146.3
16QAM 0.63 dual -83.5 -80.4 -78.5 -75.3 +22 151.5 148.4 146.5 143.3
16QAM 0.87 single -82.1 -79.5 -78.1 -72.5 +20 148.1 145.5 144.1 138.5
16QAM 0.87 dual -79.2 -76.2 -73.9 -71.5 +20 145.2 142.2 139.9 137.5
64QAM 0.75 single -78.8 -76.7 -75.2 -69.2 +18 142.8 140.7 139.2 133.2
64QAM 0.75 dual -76.1 -73.1 -71.0 -67.7 +18 140.1 137.1 135.0 131.7
64QAM 0.92 single -74.4 -72.5 -66.2 -65.0 +18 138.4 136.5 134.6 129.0
64 QAM 0.92 dual -70.2 -69.1 -70.7 -61.5 +18 134.2 133.1 130.2 125.5
327
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Mode
BPSK 0.63 single -95.1 -92.5 -90.8 -86.3 +25 166.1 163.5 161.8 157.3
QPSK 0.63 single -88.7 -87.8 -86.0 -80.6 +24 158.7 157.8 155.9 150.6
QPSK 0.87 single -85.5 -83.8 -81.6 -77.8 +23 154.5 152.8 150.6 146.8
16QAM 0.63 single -82.0 -81.3 -79.1 -75.3 +22 150.0 149..3 147.1 143.3
16QAM 0.63 dual -79.4 -77.6 -75.6 -71.7 +22 147.4 145.6 143.6 139.7
16QAM 0.87 single -78.7 -76.3 -74.7 -71.2 +20 144.7 142.3 140.7 137.2
16QAM 0.87 dual -75.1 -73.2 -71.0 -67.7 +20 141.0 139.2 137.0 133.7
64QAM 0.75 single -74.4 -72.3 -70.6 -67.9 +18 138.4 136.3 134.6 131.9
64QAM 0.75 dual -70.9 -69.5 -67.6 -64.0 +18 134.9 133.5 131.6 128.0
64QAM 0.92 single -70.9 -68.0 -66.6 -63.1 +18 134.9 132.0 130.6 127.1
64 QAM 0.92 dual -66.8 -64.6 -65.5 -58.7 +18 130.8 128.6 126.5 122.7
328
17.7.8 PTP 58600 FCC Antenna Restrictions
In FCC regions, external antennas from the list in Table 80 can be used with the
Connectorized version of the PTP 58600. These are approved by the FCC for use with the
product and are constrained by the following limit for Single/Dual Polarization Parabolic Dish
Antennas: up to 37.7 dBi per polarization or antenna.
In FCC regions when using external antennas, cable loss between the connectorized version
of the PTP 600 Series Bridge and the antenna ports must not be less than 1.2 dB.
CAUTION
Antennas not included in this table, or those having a gain greater than the specified
maximum, are strictly prohibited for use with the PTP 58600. The required antenna
impedance is 50 ohms.
Table 80 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz
Gain Flat Parabolic
(dBi) Plate Dish
Andrew Andrew 1-foot Flat Panel, 23.6 Y
FPA5250D12-N (23.6dBi)
Andrew Andrew 2-foot Flat Panel, 28 Y
FPA5250D24-N (28dBi)
Gabriel Gabriel 1-foot Flat Panel, DFPD1-52 23.5 Y
(23.5dBi)
Gabriel Gabriel 2-foot Flat Panel, DFPD2-52 28 Y
(28dBi)
MTI MTI 17 inch Diamond Flat Panel, MT- 23 Y
485009 (23dBi)
MTI MTI 15 inch Dual-Pol Flat Panel, 23 Y
MT-485025/NVH (23dBi)
MTI MTI 2 ft Directional Flat Panel, MT- 28 Y
20004 (28dBi)
MTI MTI 2 ft Flat Panel, MT-486001 (28dBi) 28 Y
RFS RFS 1-foot Flat Panel, MA0528-23AN 23 Y
(23dBi)
RFS RFS 2-foot Flat Panel, MA0528-28AN 28 Y
(28dBi)
Telectronics Teletronics 2-foot Flat Plate Antenna, 28 Y
ANT-P5828 (28dBi)
329
Gain Flat Parabolic

(dBi) Plate Dish
Andrew Andrew 2-foot Parabolic, P2F-52 29.4 Y
(29.4dBi)
Andrew Andrew 2-foot Dual-Pol Parabolic, 29.4 Y
PX2F-52 (29.4dBi)
(33.4dBi)
PX3F-52 (33.4dBi)
(34.9dBi)
PX4F-52 (34.9dBi)
(37.6dBi)
PX6F-52 (37.6dBi)
Gabriel Gabriel 2-foot High Performance 28.2 Y
QuickFire Parabolic, HQF2-52-N
Parabolic,
QF2-52-N
Parabolic,
QF2-52-N-RK
Gabriel Gabriel 2.5-foot Standard QuickFire 31.2 Y
Parabolic, QF2.5-52-N
Parabolic,
QF4-52-N
330
Gain Flat Parabolic

(dBi) Plate Dish
Parabolic,
QF4-52-N-RK
Parabolic,
QF6-52-N
Gabriel Gabriel 2.5-foot Standard Dual 31.1 Y
QuickFire Parabolic, QFD2.5-52-N
SPD2-5.2 (28.1dBi)
RadioWaves Radio Waves 2-foot Parabolic, SP2-5.2 29 Y
(29.0dBi)
SPD3-5.2 (31.1dBi)
(31.4dBi)
SPD4-5.2 (34.4dBi)
(34.8dBi)
SPD6-5.2 (37.5dBi)
(37.7dBi)
(28.3dBi)
(31.4dBi)
(34.6dBi)
331
Gain Flat Parabolic

(dBi) Plate Dish
(37.7dBi)
SPFX3-52AN(31.4dBi)
SPFX4-52AN(33.9dBi)
RFS RFS 2-foot HP Parabolic, SDF2-52AN 31.4 Y
or SDFX2-52AN (31.4dBi)
StellaDoradus StellaDoradus 45 inch Parabolic 33.8 Y
Antenna, 58PSD113
332

variant.

Operation of this product is only allowed with a License Key for Region 16
Russia
(no power limit)
Operation of this product is only allowed with a License Key for Regions 17
India or 19 (36 dBm or 4W EIRP at 30 MHz, 15 MHz and 10 MHz; and 33 dBm or
2 W EIRP at 5 MHz channel bandwidth).
PTP 59600 units may be operated in any of the regions listed in Table 82. When shipped,
PTP 59600 units are configured with a license key for Region Code 16. An alternative license
key is provided in the Deployment Guide for Region Code 17. For any other permitted region,
obtain a new license key from the reseller or distributor.

15 Unrestricted 5825 - 5925 5, 10, 15, 30 25 dBm
MHz MHz
16 Russia 5825 - 5925 5, 10, 15, 30 25 dBm

MHz MHz
17 India 5875 - 5925 10, 15, 30 MHz 36 dBm EIRP

MHz
5 MHz 33 dBm EIRP
19 India 5825 - 5875 10, 15, 30 MHz 36 dBm EIRP

MHz
5 MHz 33 dBm EIRP
333
NOTE
The 5.8 GHz license for India is addressed using both PTP 58600 and PTP 59600
frequency variants.
17.8.3.1 Russia
This system has been tested for type approval in Russia of fixed link equipment under the
heading of BPD TZS 12.
Сертификат соответствия Срок действия
ОС-1-РД-0241 с 28 октября 2008 г.
RF Band 5.825-5.925GHz

avoid interference.

ms.

users of the band.
334

166 dB
Channel)
125 miles (200km) optical line-of-sight

Range
6 miles (10km) non-line-of-sight

changes
NOTE
335
336
337
338
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Mode
BPSK 0.63 single -97.1 -94.1 -92.0 -88.7 +25 168.1 165.1 163.0 159.7
QPSK 0.63 single -90.7 -88.1 -87.1 -82.5 +24 160.7 158.1 157.1 152.5
QPSK 0.87 single -87.2 -84.4 -83.5 -79.3 +23 156.2 153.4 152.5 148.3
16QAM 0.63 single -85.0 -81.9 -81.2 -77.1 +22 153.0 149.9 149.2 145.1
16QAM 0.63 dual -81.9 -78.8 -77.5 -73.5 +22 149.9 146.8 145.5 141.5
16QAM 0.87 single -80.9 -78.0 -76.7 -72.9 +20 146.9 143.9 142.7 138.9
16QAM 0.87 dual -76.5 -73.9 -73.2 -70.0 +20 142.5 139.9 139.2 136.0
64QAM 0.75 single -77.0 -74.6 -73.6 -70.3 +18 141.0 138.6 137.6 134.3
64QAM 0.75 dual -73.1 -71.0 -70.4 -67.5 +18 137.1 135.0 134.4 131.5
64QAM 0.92 single -72.1 -71.0 -68.9 -65.7 +18 136.1 135.0 132.9 129.7
64 QAM 0.92 dual -70.2 -67.2 -66.1 -62.1 +18 134.2 131.1 130.1 126.1
339
Output
(dBm)
Channel 30
Bandwidth 5 10 15 30 All 5 10 15
MHz
Mode
BPSK 0.63 single -97.1 -94.1 -92.0 -88.7 +25 168.1 165.1 163.0 159.7
QPSK 0.63 single -88.5 -86.1 -84.4 -79.4 +24 158.5 156.1 154.4 149.4
QPSK 0.87 single -84.6 -81.9 -80.1 -76.0 +23 153.6 150.9 149.1 145.0
16QAM 0.63 single -82.5 -79.6 -77.8 -73.7 +22 150.4 147.6 145.8 141.7
16QAM 0.63 dual -78.8 -76.0 -74.1 -70.4 +22 146.8 144.0 142.1 138.4
16QAM 0.87 single -78.3 -75.1 -73.7 -70.2 +20 144.3 141.1 139.7 136.2
16QAM 0.87 dual -74.2 -71.6 -70.2 -66.9 +20 140.2 137.6 134.2 132.9
64QAM 0.75 single -74.7 -71.4 -70.2 -67.3 +18 138.7 135.4 134.2 131.3
64QAM 0.75 dual -70.9 -68.3 -66.8 -63.6 +18 134.8 132.2 130.8 127.6
64QAM 0.92 single -71.2 -68.1 -67.0 -63.3 +18 135.2 132.0 131.0 127.3
64 QAM 0.92 dual -66.7 -64.2 -62.7 -58.7 +18 130.7 128.2 126.7 122.7
340
18 FAQs
18 FAQs
Can I source and use my own PoE adaptor with the PTP 600 Series bridge? No. The
PTP 600 Series bridge uses a non-standard PoE configuration. Failure to use the Motorola
supplied Power Indoor Unit could result in equipment damage and will invalidate the safety
certification and may cause a safety hazard.
Why has Motorola launched the PTP 600 Series bridge? The PTP 600 Series bridge is the
first product to feature Multiple-Input Multiple-Output (MIMO). The PTP 600 Series solutions
allow wireless connections of up to 200km (124 miles) in near line-of-sight conditions and up
to 10km (6 miles) in deep non-line-of-sight conditions.
What is Multiple-Input Multiple-Output (MIMO)? The PTP 600 Series bridge radiates
multiple beams from the antenna - the effect of which is to significantly protect against fading
and to radically increase the probability that the receiver will decode a usable signal. When
the effects of MIMO are combined with those of OFDM techniques and a best in class link
budget, there is a significant improvement to the probability of a robust connection over a
non-line-of-sight path.
What do you mean by “non-line-of-sight”? A wireless connection between two points

without optical line-of-sight, that is, with obstructions between the antennas the transmitted
signal is still able to reach the receiver and produce a good quality link.
What else is special about the PTP 600 Series bridge ? There are many special features
built-in to the hardware of the PTP 600 Series bridge. The product offers the highest system
gain in its class through high sensitivity antennas for improved signal recovery. It also
features a radio system that operates on ultra fast digital signal processors but is controlled
by firmware giving the ability to download new firmware when enhancements become
available. The PTP 600 Series bridge has a built-in web server for advanced management
capabilities including detailed radio signal diagnosis.
In which frequency bands does the PTP 600 Series bridge operate? The Motorola point-
to-point 600 Series bridge operates in the licensed bands 2.5 GHz, 4.5 GHz, 4.8 GHz and 4.9
GHz, and in the unlicensed bands 5.4 GHz (ETSI Band B), 5.8 GHz (ETSI Band C and FCC
ISM band) and 5.9 GHz. Users must ensure that the PTP 600 Series bridge complies with
local operating regulations.
341
18 FAQs
Why does the PTP 600 Series bridge operate in the 5GHz band? The 5 GHz band offers
the dual benefits of high data throughput and good radio propagation characteristics. The
wide band of spectrum available is subdivided into several channels such that multiple
systems can operate in the vicinity without causing interference to one another.
Is the PTP 600 Series bridge an 802.11a device? No, although similar, the PTP 600 Series
bridge uses different encoding and radio transmission systems from 802.11a. In areas where
802.11a systems are operating, the PTP 600 Series bridge will detect the 802.11a radio
signals and choose a clear channel away from any interference.
How much power does the PTP 600 Series bridge transmit? At all times the PTP 600
Series bridge operates within country / region specific regulations for radio power emissions.
In addition, the PTP 600 Series bridge uses a technique known as Transmit Power Control
(TPC) to ensure that it only transmits sufficient radio power such that the other antenna can
receive a high quality signal.
How does the PTP 600 Series Bridge avoid interference from other devices nearby? At
initialization, the PTP 600 Series bridge monitors the available frequency channels to find a
channel that is clear of interference. In operation 600 Series bridge continuously monitors the
spectrum to ensure it is operating on the cleanest channel.
How does the PTP 600 Series bridge integrate into my data network? The PTP 600
Series bridge acts as a transparent bridge between two segments of your network. In this
sense, it can be treated like a virtual wired connection between the two buildings. The PTP
600 Series bridge forwards 802.3 Ethernet packets destined for the other part of the network
and filters packets it does not need to forward. The system is transparent to higher-level
management systems such as VLANs and Spanning Tree.
How does the PTP 600 Series bridge provide security for data traffic? The PTP 600
Series bridge has a range of security features. At installation time each link must be
programmed with the serial ID of its partner. The two ends of the link will only communicate
with one another, eliminating any chance of "man in the middle" attacks. Over the air security
is achieved through a proprietary scrambling mechanism that cannot be disabled, spoofed or
snooped by commercial tools.
Can I use Apple Macintosh OS X to control and monitor my 600 Series bridge? Yes, but
there are some restrictions. Mozilla 1.6 or higher is recommended.
342
19 Glossary
19 Glossary
ARP Address Resolution Protocol NLOS non-Line-of-Sight

ARQ Automatic Repeat reQuest ODU Outdoor Unit
BPSK Binary Phase Shift Keying OFDM Orthogonal Frequency Division

DC Direct Current Multiplex
Dynamic Frequency Selection IBM Compatible Personal
DFS PC
Computer
European Telecommunications PIDU Power Indoor Unit Plus
ETSI
Plus
Standards Institute PING Packet Internet Groper
FAQ Frequently Asked Question POE Power over Ethernet
GPS Global Positioning System PSU Power Supply Unit
HP Hypertext Transfer Protocol PTP Point-to-Point
Identity Quadrature Amplitude
ID QAM
Modulation
Institute of Electrical and
IEEE RAM Random Access Memory
Electronic Engineers
IP Internet Protocol STC Space Time Coding
IQ In phase / Quadrature STP Shielded Twisted Pair
ISM Industrial Scientific and Medical TCP Transmission Control Protocol
International
ITU TPC Transmit Power Control
Telecommunications Union
LAN Local Area Network URL Universal Resource Location
MAC Medium Access Control Layer USA United States of America
MDI Medium Dependent Interface UTP Unshielded Twisted Pair
Medium Dependent Interface Ultraviolet
MDIX UV
Crossover
VLAN Virtual Local Area Network
343
19 Glossary
344
Index
Index
Adaptive Modulation 43 Spectrum Management 148
AES Encryption 248 Telecoms 112
Alarm 88, 89, 90 Web Pages 98

Wireless 128
Alarms 87
Connecting 203
Diagnostics 161
at ODU 70, 71
Alignment 80, 201
at PIDU 73
Antenna 191, 193, 198, 201
PIDU to ODU 67
Antenna Restrictions
to Network 75
PTP 54600 312
Connectorized Variant 190
PTP 58600 329
Connectors 199
Balun 223
Data Rates 226
Band Edge Power Reduction 326
Deployment 14
Bandwidth 38
Brackets 25
Description
Cable
Preparation 67
of PTP 600 13
Routing 72
diagnostics 96, 166
Cable Loss 194
Diagnostics 161, 164
Download 166
Cables 23, 199
Plotter 165
for Antennas 202
Dimensions 266
Channel Bandwidth 28, 38
Disarm 123, 135
channels 34, 155
Disarm ODU 83, 216
Channels 143
Disclaimer 260
Barring 149
Distances 8
History 151
E1/T1
Clock 163
Configuration 126
Compliance 10, 267, 268
Mast or Tower 55
Conditions of Use 256
ODU connection 221
Configuration 27, 107, 172 Wall Installation 56
Confirmation of 133 E1/T1 links
Telecoms Circuits 33
Erasing 176
Eire 12
Ethernet 107
EIRP 195
IP 124
Emissions
Manual 121
I
Index
PTP 25600 274 Grounding 73

PTP 45600 281 Histogram 96
PTP 48600 289 Hoist 66
PTP 49600 297
Home Page 86
PTP 54600 307
HTTP 159
PTP 58600 323
IC Notification
Encryption 248
PTP 49600 296
Environmental 269
PTP 54600 303
Ethernet 104, 115
PTP 58600 319
Activity 184
Immunity 268
Configuration 107, 175
Installation 61
Frames 26
Port 19
Specifications 266
Ethernet Connection 16
E1/T1 224
Ethernet frames 100
Graphical 137
Ethernet LED 18 LPU 48
ETSI 10 Wiring for LPU 51
EU Notification Installation Pages 120
PTP 54600 304 Interference 11
PTP 58600 320 IP
FAQs Configuration 175
General 341 IP address 79
Wireless Link 252
IP Addresses 79
Fault Finding 180
LAN
FCC 10
Configuration 103
FCC Notification
Lateral Force 41
PTP 25600 272
LED
PTP 49600 296
Power 182
PTP 54600 303
LEDs 18
PTP 58600 319
Remote 23
Fixed Frequency 153
Legal
Frequencies 15
Notices 255
Frequency Variants 16
Legal Disclaimer 62
Glossary 343
license 15
GPS Sync Unit 57, 58, 59, 60
License Agreement 255
GPS Synchronization Unit 187, 207
License Key 167
Graphical Installation 137
AES 249
II
Index
Licenses 36 Metrics
PTP 25600 271 Viewing 152
PTP 45600 279 MIB 159
PTP 48600 287 Modulation 43
PTP 49600 295 Motorola Contacts 2, 4
PTP 54600 302
Mounting 25, 63
PTP 58600 317
PTP 59600 333
PIDU 75
Lightning 13, 24
Network 16
Lightning Protection 45
Networking 28
and E1/T1 224
Non Line Of Sight (NLOS) 26, 28
Obstacles 39
PTP and 24
Test after a strike 189 OfCom 12
Lightning Protection Unit (LPU) Optimization

Fitting 72 of the Link 32
Limits 11 Outdoor Unit (ODU)
Line Of Sight (LOS) 26, 28 Description 17

Mounting 63
Link Budget
Site Selection 40
Output Power 44
Link Loss 44
Password 167
PTP 25600 277
PTP 45600 285 Path Loss 43
PTP 48600 293 PIDU
PTP 49600 299 Description 18
PTP 54600 310 Site Selection 40
PTP 58600 327 Planning 35
PTP 59600 339 of the PTP Link 39
Link Mode Optimization 32 Power
Link Symmetry 28 Alternative Configurations 21
LINKPlanner 39 PTP 25600 277
LPU PTP 45600 285

PTP 48600 293
Configurations 52
PTP 49600 299
MAC Address 173
PTP 54600 310
Management 27
PTP 58600 327
Remote 158
PTP 59600 339
Mast Installation 53, 55
Supply 19
Master and Slave 149
Power Compliance 8
Measurements 143
III
Index
Power LED 18 PTP 25600 273
Power Output 44 PTP 45600 280
Power Supply 267 PTP 48600 288

PTP 49600 296
Powering Up 79
PTP 54600 305
Priorities 100
PTP 58600 322
Properties 169
PTP 59600 334
PTP 25600
Range 39
Information 270
Range Adjustment 239
Spectrum Management 157
Reboot 170, 172, 179
PTP 45600
Reboot ODU 213
Information 279
Recovery 171
PTP 48600
Recovery Switch
Information 287
Remote 23
PTP 49600
Reference Information 265
Information 295
Region Codes 36
PTP 54600
PTP 25600 271
Information 301
PTP 45600 279
PTP 58600
PTP 48600 287
Information 315
PTP 49600 295
PTP 59600
PTP 54600 302
Information 333
PTP 58600 317
PTP LINKPlanner 39
PTP 59600 333
QoS configuration 100
Regulations 10
Questions 252 Connectorized Variant 197
Radar Examples 11
Avoidance 34, 155 Regulatory
radio 10, 11, 316 Notices 255
Radio 188 Regulatory Compliance
Radio Certifications PTP 25600 272
PTP 25600 274 PTP 49600 296
PTP 45600 281 PTP 54600 303
PTP 48600 289 PTP 58600 319
PTP 49600 297 PTP 59600 334
PTP 54600 307 Regulatory Limits
PTP 58600 323 PTP 25600 270
Radio Link PTP 45600 279
Starting Up 80 PTP 48600 287
Radio Specifications PTP 49600 295
IV
Index
PTP 54600 301 Spectrum Settings

PTP 58600 315 PTP 25600 274
PTP 59600 333 PTP 45600 281
Regulatory Notices 265 PTP 48600 290
Repair 4 PTP 49600 298
Reset 172, 175 PTP 54600 308
Resistances PTP 58600 324

PTP 59600 335
E1/T1 225
RJ45 185 Statistics 114
Restore 107 Status Page 91
RJ45 Connectorized Variant 191
Color Coding 217 Support 62

Testing 185 Surge 13, 24, 72
RJ45 Cable Synchronization
Dressing 77 TDD 30
RTTT 37 System Administration

Safety Password 167
Electrical 5 System Administration Pages 97

RF 7 TDD 26, 29, 129
Safety Loop 66 TDD Synchronization 206
Save 107 Configuration 210
Screens 84 Status 214
Service 4 Telecoms 33, 112, 267
Sites Telecoms Interface 126

Selection 40 Telnet 159
SMTP 162 Testing
SNMP 159, 162 Hardware 180
SNTP 163 Radio Link 188

TFTP 253
Software 172
Connectorized Variant 191 Third Party Software 262
License Key 167 Threshold
TFTP Upgrade 253 PTP 25600 277
Upgrades 28 PTP 45600 285
Upgrading 138, 173 PTP 48600 293
Specifications 265 PTP 49600 299
Spectrum Management 143, 194 PTP 54600 310

PTP 58600 327
Master and Slave 144
PTP 59600 339
Spectrum Planning 35
Thresholds 44
V
Index
Throughput 226, 285, 293 VLAN 105

Time Division Duplex (TDD) 29 Wall Installation 54
Tools 62, 199 Warning 88, 89, 90
Tower Installation 53, 55 Warranty 5
Traffic classes 100 Weather 42
Transmit Power 82 Weatherproofing 203
Transmit Power Reduction 326 Web Pages 84
Troubleshooting 180 Webpage Properties 169
Upgrade 138, 172, 173 Weight 266
User Interface 84 Wind Loading 40
User Support 2, 4 Zones 45
Variants 16
VI
Index
Unit A1, Linhay Business Park

Eastern Road, Ashburton
Devon, TQ 13 7UP, UK
Telephone Support: +1 877 515-0400 (Worldwide)
+44 808 234 4640 (UK)
www.motorola.com/ptp
VII
MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein
are trademarks of Motorola, Inc. ® Reg. US Pat & Tm. Office. All other product or
service names are the property of their respective owners. © 2007 Motorola, Inc. All
rights reserved.

Motorola - Manual - PONTO A PONTO - PTP 600 ANTENA INTEGRADA E EXTERNA

Uploaded by

Copyright:

Available Formats

Motorola - Manual - PONTO A PONTO - PTP 600 ANTENA INTEGRADA E EXTERNA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Motorola - Manual - PONTO A PONTO - PTP 600 ANTENA INTEGRADA E EXTERNA

Uploaded by

Copyright:

Available Formats

PTP 600 Series

MOTOROLA POINT-TO-POINT WIRELESS SOLUTIONS

Point-to-Point Wireless Bridges – PTP 600 Series

Software Release PTP 600-08-xx

System User Guide

July 14th, 2009

© 2006-2009 Motorola, Inc. All rights reserved.

2.7.4 Remote Connectors and Jumpers ............................................................................... 19

4.5.1 Range and Obstacles .................................................................................................. 39

6.4.3 Hoist and Safety Loop.................................................................................................. 66

7.7.3 Current Installation Summary .................................................................................... 123

7.11.2 CSV Download........................................................................................................... 166

10.5.1 Cable Losses (FCC Regions Only)............................................................................ 198

12.4 Routing the Cable................................................................................................................. 223

16.1.10 Disclaimer .................................................................................................................. 260

17.4.4 PTP 48600 Emissions and Radio Certifications ........................................................ 289

18 FAQs ............................................................................................................................................. 341

Figure 2 - Mod Record Label................................................................................................................ 16

Figure 4 - Power Indoor Unit (PIDU Plus PTP 300/500/600 Series).................................................... 18

Figure 5 – PIDU Plus Recovery Switch Location ................................................................................. 19

Figure 6 – PIDU Plus Power Input........................................................................................................ 20

Figure 7 – Relationship Between DC Voltage and Cable Length ........................................................ 21

Figure 8 - External DC Supply Only ..................................................................................................... 22

Figure 9 - External DC Supply and AC Supply..................................................................................... 22

Figure 10 - External DC Supply and Redundant AC Supply ................................................................ 22

Figure 11 - Remote LED and Recovery Switch Wiring ........................................................................ 23

Figure 12 – PTP 600 Series Bridge Layer Diagram ............................................................................. 27

Figure 13 - Co-location of Links Interference Problem - A Simple Example ........................................ 29

Figure 14 - TDD Synchronization And Co location Example................................................................ 30

Figure 16 - ODU mounted in Zones A & B ........................................................................................... 46

Figure 17 – Using a Finial to extend Zone B ........................................................................................ 46

Figure 18 – Example of PTP-LPU Configuration – Option 1 (Back-to-Back Recommended) ............. 48

Figure 19 - PTP-LPU - Installation Option 2 (Using U-Bolt) ................................................................. 49

Figure 20 - PTP LPU Full Kit ................................................................................................................ 50

Figure 21 - Simplified Circuit Diagram.................................................................................................. 51

Figure 22 - Typical Mast or Tower Installation ..................................................................................... 53

Figure 23 - Typical Wall Installation...................................................................................................... 54

Figure 24 – Mast or Tower Installation with E1/T1 ............................................................................... 55

Figure 25 - Wall Installation with E1/T1 ................................................................................................ 56

Figure 26 – Mast or Tower Installation with GPS Sync Unit................................................................. 57

Figure 27 –Wall Installation with GPS Sync Unit.................................................................................. 58

Figure 29 - Wall Installation with GPS Sync Unit and E1/T1................................................................ 60

Figure 31 – ODU Bracket Strap............................................................................................................ 64

Figure 32 – ODU Mounting Bracket ..................................................................................................... 64

Figure 33 - ODU Mounted on Pole ....................................................................................................... 65

Figure 34 - Integral Safety Loop ........................................................................................................... 66

Figure 35 - Correct Cable Preparation for the Recommended Cable .................................................. 68

Figure 36 - Completed ODU Connector ............................................................................................... 69

Figure 37 - Correct and Incorrect Tightening of Cable Gland .............................................................. 69

Figure 38 – ODU PIDU Plus Connexion............................................................................................... 70

Figure 39 - Connecting the PIDU Plus+ to the ODU ............................................................................ 71

Figure 40 - Disconnecting the ODU...................................................................................................... 72

Figure 41 - Connecting the ODU to the PIDU Plus+ ............................................................................ 74

Figure 42 - Making the Network Connection at the PIDU Plus ............................................................ 75

Figure 43 - Mounting the PIDU Plus..................................................................................................... 76

Figure 44 - Correct and Incorrect RJ45 Cable Dressing ...................................................................... 77

Figure 45 – PIDU Plus Drip Loop Configuration................................................................................... 78

Figure 46 - Menu Navigation Bar.......................................................................................................... 85

Figure 47 - System Summary Page ..................................................................................................... 86

Figure 48 - Alarm Warning Triangle ..................................................................................................... 87