PTP LINKPlanner

User Manual

MOTOROLA POINT-TO-POINT WIRELESS SOLUTIONS

 Motorola PTP LINKPlanner

User Manual

April 14th, 2008

Ref: PHN-1168-00.04

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 500 is a trademark of Motorola, Inc. All other
product or service names are the property of their respective owners.

2008 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.

1
Contents
1 Introduction ......................................................................................................................... 10
1.1 Interpreting Typeface and Other Conventions ...................................................................... 11
1.2 Getting Additional Help ......................................................................................................... 13
1.3 Sending Feedback ................................................................................................................ 13
2 Quick Tutorial ...................................................................................................................... 14
2.1 Getting Started ...................................................................................................................... 14
2.2 Creating Project, Sites and Link............................................................................................ 14
2.3 Updating Profile and Obstructions ........................................................................................ 18
2.4 Adjusting Configuration and Requirements .......................................................................... 20
3 Installing PTP LINKPlanner................................................................................................ 24
3.1 Windows Installation.............................................................................................................. 24
3.2 Mac Installation ..................................................................................................................... 28
4 Using PTP LINKPlanner...................................................................................................... 29
4.1 Getting Started ...................................................................................................................... 29
4.1.1 Options (Preferences on Mac) .............................................................................................. 29
4.1.2 Main Screen .......................................................................................................................... 31
4.1.3 Project Navigation Tree......................................................................................................... 32
4.1.4 Building a Project .................................................................................................................. 33
4.1.5 Importing Path Data .............................................................................................................. 33
4.2 Projects ................................................................................................................................. 34
4.2.1 Inserting New Projects .......................................................................................................... 34
4.2.2 Viewing and Updating Projects ............................................................................................. 34
4.2.3 Project Page.......................................................................................................................... 35
4.2.3.1 Equipment Defaults ............................................................................................................... 35
4.2.3.2 Local/Remote Defaults .......................................................................................................... 35
4.2.3.3 Customer Information............................................................................................................ 36
4.2.3.4 Map ....................................................................................................................................... 36
4.2.4 Saving Projects ..................................................................................................................... 36
4.3 Sites ...................................................................................................................................... 37
4.3.1 Inserting New Sites ............................................................................................................... 37
4.3.1.1 Importing Sites from Google Earth (.KML) ........................................................................ 37
4.3.1.2 Importing Sites from a .CSV File........................................................................................... 37
4.3.1.3 Manually Inserting Sites ........................................................................................................ 38
4.3.2 Displaying the Sites List ........................................................................................................ 39

2
4.3.3 Viewing and Updating Sites .................................................................................................. 39
4.3.3.1 Site Details ............................................................................................................................ 39
4.3.3.2 Links to Site........................................................................................................................... 40
4.3.3.3 Site Links Graph.................................................................................................................... 40
4.4 Links ...................................................................................................................................... 41
4.4.1 Inserting New Links ............................................................................................................... 41
4.4.2 Displaying the Links List........................................................................................................ 42
4.4.3 Viewing and Updating Links.................................................................................................. 42
4.4.4 Obtaining Link Profiles .......................................................................................................... 43
4.4.5 Updating Profiles with Obstructions ...................................................................................... 45
4.4.5.1 Identifying Obstructions......................................................................................................... 45
4.4.5.2 Editing the Profile .................................................................................................................. 46
4.5 Evaluating Link Performance ................................................................................................ 48
4.5.1 Link Description..................................................................................................................... 48
4.5.2 Equipment ............................................................................................................................. 49
4.5.3 Profile .................................................................................................................................... 50
4.5.4 Configuration of Local and Remote Ends ............................................................................. 51
4.5.5 Performance Summary ......................................................................................................... 53
4.5.5.1 Link Loss Summary............................................................................................................... 53
4.5.5.2 Receive Performance at Local .............................................................................................. 54
4.5.5.3 Receive Performance at Remote .......................................................................................... 54
4.5.6 Performance Details.............................................................................................................. 55
4.5.7 Flags...................................................................................................................................... 56
4.6 Exporting Data....................................................................................................................... 57
4.6.1 Links (CSV) ........................................................................................................................... 57
4.6.2 Sites (CSV)............................................................................................................................ 57
4.6.3 Site (CSV) ............................................................................................................................. 57
4.6.4 Google Earth (KML)........................................................................................................... 57
4.7 Creating Reports ................................................................................................................... 58
4.7.1 Project (one page or multipage)............................................................................................ 58
4.7.2 Links Table ............................................................................................................................ 58
4.7.3 Link........................................................................................................................................ 58
4.7.4 Site ........................................................................................................................................ 58
5 Path Loss Considerations.................................................................................................. 59
5.1 Free Space Path Loss........................................................................................................... 60
5.2 Excess Path Loss.................................................................................................................. 60

3
5.2.1 Fresnel Zone ......................................................................................................................... 61
5.3 Fade Margin .......................................................................................................................... 62
5.4 Maximum Path Loss.............................................................................................................. 63
5.5 Paths Over Sea or Very Flat Ground .................................................................................... 63
6 PTP500 Equipment Features.............................................................................................. 65
7 Path Profiles ........................................................................................................................ 66
7.1 PTP Path Profiler................................................................................................................... 66
7.2 Path Profile E-mail................................................................................................................. 69
8 Import File Formats............................................................................................................. 70
8.1 Path from Hydra - no Site Names (*.pth) .............................................................................. 70
8.2 Path from Hydra - with Site Names (*.pth) ............................................................................ 70
8.3 Points from Comma Delimited File (*.csv) ............................................................................ 70
9 SRTM Technical Guide ....................................................................................................... 71
10 Legal Notices ....................................................................................................................... 73
10.1 Motorola Inc. End User License Agreement ......................................................................... 73
10.1.1 Definitions.............................................................................................................................. 73
10.1.2 Grant of License .................................................................................................................... 73
10.1.3 Conditions of Use .................................................................................................................. 73
10.1.4 Title; Restrictions................................................................................................................... 75
10.1.5 Confidentiality........................................................................................................................ 75
10.1.6 Right to Use Motorolas Name .............................................................................................. 76
10.1.7 Transfer ................................................................................................................................. 76
10.1.8 Updates ................................................................................................................................. 76
10.1.9 Maintenance.......................................................................................................................... 76
10.1.10 Disclaimer.............................................................................................................................. 76
10.1.11 Limitation of Liability .............................................................................................................. 77
10.1.12 U.S. Government................................................................................................................... 77
10.1.13 Term of License..................................................................................................................... 77
10.1.14 Governing Law ...................................................................................................................... 78
10.1.15 Assignment............................................................................................................................ 78
10.1.16 Survival of Provisions ............................................................................................................ 78
10.1.17 Entire Agreement .................................................................................................................. 78
10.2 Third Party Software.............................................................................................................. 79
10.3 Limit of Liability...................................................................................................................... 82
11 Glossary ............................................................................................................................... 83

4
5
List of Figures
Figure 1 Tutorial: Inserting Site 1 ...................................................................................................... 15
Figure 2 Tutorial: Inserting Site 2 ...................................................................................................... 15
Figure 3 Tutorial: Inserting Link ......................................................................................................... 16
Figure 4 Tutorial: Requesting Profiles ............................................................................................... 17
Figure 5 Tutorial: Equipment ............................................................................................................. 17
Figure 6 Tutorial: Path Profile............................................................................................................ 18
Figure 7 Tutorial: Profile Editor.......................................................................................................... 19
Figure 8 Tutorial: Path Profile with Obstructions ............................................................................... 19
Figure 9 - Tutorial: Adjust Local End .................................................................................................... 20
Figure 10 - Tutorial: Adjust Remote End .............................................................................................. 20
Figure 11 - Tutorial: Performance Unacceptable at Local End ............................................................ 21
Figure 12 - Tutorial: Performance Unacceptable at Remote End ........................................................ 21
Figure 13 - Tutorial: Adjust Local End Again........................................................................................ 22
Figure 14 - Tutorial: Adjust Remote End Again.................................................................................... 22
Figure 15 - Tutorial: Performance Acceptable at Local End................................................................. 23
Figure 16 - Tutorial: Performance Acceptable at Remote End ............................................................ 23
Figure 17 Setup Wizard Welcome Page ........................................................................................... 24
Figure 18 Select Destination Location page...................................................................................... 25
Figure 19 Select Start Menu Folder page ......................................................................................... 26
Figure 20 Ready to Install page......................................................................................................... 27
Figure 21 Installation Completion page ............................................................................................. 28
Figure 22 - Options/Preferences Page ................................................................................................. 30
Figure 23 Main Screen ...................................................................................................................... 31
Figure 24 - Navigation Tree.................................................................................................................. 32
Figure 25 Equipment Defaults ........................................................................................................... 35
Figure 26 Local/Remote Defaults ...................................................................................................... 35
Figure 27 - Customer Information......................................................................................................... 36
Figure 28 - Project Node NLOS Short Distance in navigation tree ...................................................... 36
Figure 29 New Site page ................................................................................................................... 38
Figure 30 - Sites List............................................................................................................................. 39
Figure 31 Details in Site Page ............................................................................................................ 39
Figure 32 - Links in Site Page .............................................................................................................. 40
Figure 33 - Links Graph in Site Page ................................................................................................... 40
Figure 34 - New Link Page ................................................................................................................... 41
Figure 35 - Links List ............................................................................................................................ 42

6
Figure 36 - Request Profiles Page ....................................................................................................... 43
Figure 37 - Import .dat Page................................................................................................................. 44
Figure 38 - Google Earth Aerial Photograph with High Points and Ruler Tool................................. 45
Figure 39 - Profile Visualization Chart .................................................................................................. 46
Figure 40 - Profile Editor....................................................................................................................... 47
Figure 41 Profile updated with tree obstruction (in green) ................................................................ 47
Figure 42 Link Description................................................................................................................. 48
Figure 43 - Equipment .......................................................................................................................... 49
Figure 44 - Profile with tree .................................................................................................................. 50
Figure 45 - Configuration of Local and Remote ends (local shown) .................................................... 51
Figure 46 - Performance Summary ...................................................................................................... 53
Figure 47 - Performance Details........................................................................................................... 55
Figure 48 - Flags................................................................................................................................... 56
Figure 49 - Free Space Path Loss at 5.8GHz ...................................................................................... 60
Figure 50 - Fresnel Radius for Zone 0.5............................................................................................... 62
Figure 51 - Fade Margin vs Excess Path Loss for 99.99% Link Availability ........................................ 63
Figure 52 - Propagation Over The Sea ................................................................................................ 64
Figure 53 - PTP Path Profiler web page............................................................................................... 68

7
List of Tables
Table 1 - Font types ............................................................................................................................ 11
Table 2 - Admonition types................................................................................................................... 12

8
List of Equations
Equation 1 - Path Loss ......................................................................................................................... 59
Equation 2 - Fresnel Zone Radius........................................................................................................ 61

9
1 Introduction
With the PTP500 Series equipment you are provided with a PTP LINKPlanner to help predict
where and how equipment will work. The PTP LINKPlanner performs calculations in
accordance with ITU-R P.526-9 and ITU-R P.530-10. The facilities provided are:
Path profile entry Maximum EIRP adjustment.
Obstruction entry. Antenna and feeder type selection.
Saving and recalling paths. Space diversity.
Path visualization. Link optimizations.
Path loss. Import from Hydra.
Link reliability. Link symmetry control.
Average data rate. Power asymmetry.
Reliability for a given data rate. Region adjustment.
Maximum power adjustment. Site entry.
Site connections. Link connections.
Path profile import. Output Reports.

The Motorola PTP500 Series of point-to-point wireless Ethernet bridges are designed to
operate in non-line-of-sight (NLoS) and line-of-sight (LoS) environments. Link planning and
estimation enables a link of known quality to be installed. This involves the acquisition of path
profile data and use of the PTP LINKPlanner to predict the data rates and reliability over this
path, through adjustment of antenna height and RF power. When the link is installed the
mean path loss can be checked to confirm these data rates and reliability performance.

This version of the PTP LINKPlanner only applies to the PTP500 bridge.

The PTP LINKPlanner is an application that runs on Windows or Macintosh. It performs the
calculations from the ITU recommendations ITU-R P.526-9 and ITU-R P.530-10 to predict
NLoS and LoS paths for anywhere in the world. Path profile data can be obtained in a number
of different ways depending upon global location. Motorola provides a method for obtaining
path profile data; see section 7 Path Profiles. Trees and buildings (obstructions) will modify
this profile, and often the path must be surveyed to establish the correct estimation.

The PTP LINKPlanner provides results specific to the PTP500 family of wireless bridges,
giving the data rates and reliability that can be expected given the specific design features of
these products.

10
1.1 Interpreting Typeface and Other Conventions

This document employs distinctive fonts to indicate the type of information, as described in
Table 1.

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

Table 1 - Font types

This document employs 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.

Use this table and the Glossary to aid in interpreting the technical acronyms used throughout
this User Guide.

This document also employs a set of consistently used admonitions. Each type of admonition
has a general purpose that underlies the specific information in the box. These purposes are
indicated in Table 2.

11
Admonition
General Message
Label

Note Informative content that may:

Defy common or cursory logic.
Describe a peculiarity of the 500 Series solutions implementation.
Add a conditional caveat.
Provide a reference.
Explain the reason for a preceding statement or provide background
for what immediately follows.
Recommendation Suggestion for an easier, quicker, or safer action or
practice.

Important Informative content that may:

Identify an indication that you should watch for.
Advise that your action can disturb something that you may not want
disturbed.
Reiterate something that you presumably know but should always
keep in mind.

Caution! A notice that the risk of harm to equipment or service exists.

Warning! A notice that the risk of harm to person exists.

Table 2 - Admonition types

12
1.2 Getting Additional Help

To get information or assistance as soon as possible for problems that you encounter, use
the following sequence of action:

1. Search this document, the user manuals that support the modules, and the software
release notes of supported releases:

a. In the Table of Contents for the topic.

1
b. In the Adobe Reader search capability for keywords that apply.

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:

the software releases,

the configuration of software features.

5. Escalate the problem to Motorola Technical Support as follows. You may either:

a. Send e-mail to support.ptp@motorola.com

b. 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.3 Sending Feedback

We welcome your feedback on the PTP 500 system documentation

mailto:support.ptp@motorola.com. This includes feedback on the structure, content,
accuracy, or completeness of our documents, and any other comments you have.

1
Reader is a registered trademark of Adobe Systems, Incorporated.

13
2 Quick Tutorial
This section is a quick tutorial for experienced Windows or Mac users. It shows you how to
create a project to analyse the performance of a single link between two sites.

In this tutorial, you will:

Install PTP LINKPlanner, start it, then set general preferences.

Create a project with two sites and one link.

Obtain the path profile for the link and update it with obstructions.

Adjust the antennas at both ends of the link and confirm that the selected equipment
will meet the performance requirements.

2.1 Getting Started

To get started:

1. Install the software in the usual way (see section 3).

2. Start the application.

3. Enter the correct details in the Options/Preferences page (see section 4.1). Ensure
that Email address and Network Settings are correct.

2.2 Creating Project, Sites and Link

You are now ready to plan your first link. Follow these steps:

1. Click on the New Project icon . The Project page is displayed.

2. Click on the toolbar icon Save Project and save the project as Tutorial.ptpprj.

3. Click on the New Site icon . The Add New Site page is displayed. Enter the data
shown in Figure 1 and click OK.

14
 Figure 1 Tutorial: Inserting Site 1

4. Click on the New Site icon again. The Add New Site page is displayed. Enter
the data shown in Figure 2 and click OK.

Figure 2 Tutorial: Inserting Site 2

5. Click on the New Link icon . The Add New Link page is displayed. Select the two
sites shown in Figure 3 and click OK.

15
 Figure 3 Tutorial: Inserting Link

6. Select Project, Get Profiles. The Request Profiles page is displayed. The link is
already ticked as shown in Figure 4. Click OK.

16
 Figure 4 Tutorial: Requesting Profiles

The profile request is sent to the Motorola PTP Path Profiler. It may take about 5
minutes before PTP Path Profiler sends the email containing the profile to your inbox.

7. While you are waiting for your path profile email, you can update your link with Band,
License, Optimisation and Master (Figure 5).

Figure 5 Tutorial: Equipment

8. Click on the toolbar icon Save Project .

17
2.3 Updating Profile and Obstructions

Obtain the path profile for the link and update it with obstructions:

1. Review you email inbox after about 5 minutes. When you find an email entitled
Motorola PTP Path Profile Do Not Reply, open it. Double-click on the attached file
North_Middle_School_to_Park_Lane_Elementary.dat and select Open. The
profile in PTP LINKPlanner is automatically updated with the information from the .dat
file.

2. Review the profile (Figure 6).

Figure 6 Tutorial: Path Profile

3. Double-click on the profile. The Profile Editor is displayed. Enter a 4 metre high
Obstruction at Range 0.501 km and a 3.5 metre high Obstruction at Range 0.678 km
(Figure 7).

18
 Figure 7 Tutorial: Profile Editor

4. Review the profile with obstructions (Figure 8).

Figure 8 Tutorial: Path Profile with Obstructions

19
 5. Click on the toolbar icon Save Project .

2.4 Adjusting Configuration and Requirements

Adjust the antennas at both ends of the link and confirm that the selected equipment will meet
the performance requirements:

1. Adjust the Antenna Heights to given values and add Interference Density as shown in
Figure 9 and Figure 10.

Figure 9 - Tutorial: Adjust Local End

Figure 10 - Tutorial: Adjust Remote End

20
2. Put in given requirements in the data rate boxes and observe that the predicted
values are now red because they are less then required values (Figure 11 and Figure
12).

Figure 11 - Tutorial: Performance Unacceptable at Local End

Figure 12 - Tutorial: Performance Unacceptable at Remote End

21
3. Select different antennas and change Antenna Heights (Figure 13 and Figure 14).

Figure 13 - Tutorial: Adjust Local End Again

Figure 14 - Tutorial: Adjust Remote End Again

22
4. Confirm that the predicted values are no longer red (Figure 15 and Figure 16).

Figure 15 - Tutorial: Performance Acceptable at Local End

Figure 16 - Tutorial: Performance Acceptable at Remote End

This means that the performance is now acceptable and the selected equipment can
be purchased.

5. Click on the toolbar icon Save Project .

23
3 Installing PTP LINKPlanner

3.1 Windows Installation

Download and run LinkPlannerSetup.999.exe (where 999 is version identity).

The Installation page is displayed (Figure 17).

Figure 17 Setup Wizard Welcome Page

Click Next. The Select Destination Location page is displayed (Figure 18).

24
 Figure 18 Select Destination Location page

If a different folder is required, click Browse and select the required folder. Click Next to
continue. The Select Start Menu Folder page is displayed (Figure 19).

25
 Figure 19 Select Start Menu Folder page

If a different folder is required for the shortcuts, click Browse and select the required folder.
Click Next to continue. The Ready to Install page is displayed (Figure 20).

26
 Figure 20 Ready to Install page

If the Destination location and Start Menu are correct, click Install. The installation progress
page is displayed, followed by the Completion page (Figure 21).

27
 Figure 21 Installation Completion page

Click Finish. Software installation is now complete.

3.2 Mac Installation

Install using the .dmg file provided. Opening the .dmg file reveals the PTP LINKPlanner
application. This should be dropped into your application folder. Open the application folder
and find the PTP LINKPlanner. Open the application to start.

28
4 Using PTP LINKPlanner

4.1 Getting Started

Start PTP LINKPlanner. The Main Screen is displayed (Figure 23).

Before using the application, you must set Options/Preferences.

4.1.1 Options (Preferences on Mac)

The Options/Preferences page (Figure 22) must be used to enter personal information, select
units and choose network settings.

To open the Options/Preferences page:

In Windows, select Tools, Options.

In Mac, open Preferences.

29
 Figure 22 - Options/Preferences Page

Personal Information: Enter contact details for the person who prepares link plans on behalf
of the customer. The email address is used to obtain Path Profiles. Occasionally your
business email server may presume Path Profiles to be spam and reject them.
Units: Select the required units for Height, Length, Latitude and Longitude.
Network Settings: Select options for connecting to the network. Proxy settings are
sometimes required inside organisations. These may be obtained automatically from your
computer system settings. If this does not work satisfactorily, then the specific settings may
be entered here. The Proxy Password is not held or transmitted in a secure manner.

30
4.1.2 Main Screen

When PTP LINKPlanner is started, the Main Screen is displayed (Figure 23). This contains:

Left hand panel: the project navigation tree. This is blank until one or more projects
are opened.

Right hand panel: the area for viewing and editing projects, sites and links. This
initially displays information about the application and links for opening new and
recent projects.

Figure 23 Main Screen

31
4.1.3 Project Navigation Tree

When one or more projects are open, you can navigate between sites and links using the tree
in the left hand panel. This example (Figure 24) shows two open projects.

Figure 24 - Navigation Tree

Use the + and boxes to open and close each level: project, site and link. Click on a node to
open it for viewing and updating:

If you click on a project node, for example NLOS Short Distance, the Project page is
displayed (4.2.3).

If you click on a Sites node, the list of all sites within the project is displayed (4.3.2).

If you click on an individual site node, for example North Middle School, the Site
page is displayed (4.3.3).

If you click on a Links node, the list of all links within the project is displayed (4.4.2).

If you click on an individual link node, for example North Middle School to Park
Lane Elementary School, the Link page is displayed (4.5).

When a project name is displayed in bold in the navigation tree, this means that project
details have been inserted or updated but not yet saved. To save a project, select File, Save

(or Save As) or click on the toolbar icon . All project, site and link data is saved. The
project name reverts to normal typeface when saved.

32
4.1.4 Building a Project

To build a project to model a network, follow this process:

1. Create the project and enter project defaults see 4.2.

2. Insert sites see 4.3.

3. Insert links, create link profiles and enter obstructions see 4.4.

4. Use the Link page to evaluate the predicted performance of links see 4.5.

4.1.5 Importing Path Data

If path data is available in Hydra or PTP files, it can be imported and used to populate a
project with sites, links and profiles.

Before importing path data, create the project and enter defaults. Path data can then be
imported from two sources (if available):

Hydra files contain data for sites, links, profiles and obstructions. Select File, Import,
Path from Hydra (.pth).

PTP files contain data for sites, links and profiles. Select File, Import, PTP Path
(.dat).

33
4.2 Projects

A project is a set of data about an individual wireless link or a wireless network. It may contain
two or more sites and links between those sites. Projects are saved as .ptpprj files. The PTP
LINKPlanner allows the user to create, save and edit project files. The user can open one
project at a time, or two or more concurrent projects.

4.2.1 Inserting New Projects

To create a new Project, either select File, New Project (Ctrl+N), or click on the New
Project icon:

The Project page is displayed.

4.2.2 Viewing and Updating Projects

Existing projects can be opened in the following ways:

Select File, Open (Ctrl+O).

Click on the Open Project icon .

Select File, Recent Projects and select from the list.

The Project page is displayed.

34
4.2.3 Project Page

Use this page to enter the equipment and antenna defaults that apply to all links in the
project. You can vary these defaults values in the Links Page (4.5) for each link. Also, enter
details of the project customer on this page.

4.2.3.1 Equipment Defaults

Select the Equipment Defaults for the project (Figure 25). See 4.5.2 for definitions of the
fields.

Figure 25 Equipment Defaults

4.2.3.2 Local/Remote Defaults

Select the Local and Remote site antenna defaults for the project (Figure 26). See 4.5.4 for
definitions of the fields.

Figure 26 Local/Remote Defaults

35
4.2.3.3 Customer Information

Enter details of the customer for whom this plan is being prepared (Figure 27). This data will
appear in the reports if it is not blank.

Figure 27 - Customer Information

4.2.3.4 Map

This is a simple map of the sites in this project (red) and links (green). It is not populated until
sites and links are entered.

4.2.4 Saving Projects

Save the project by selecting File, Save (or Save As) or clicking on the toolbar icon Save

Project . Enter the required project name, for example NLOS Short Distance.ptpprj.
PTP LINKPlanner now uses the .ptpprj file name as the project name.

The project name is now displayed in the project node in the navigation tree (Figure 28).

Figure 28 - Project Node NLOS Short Distance in navigation tree

36
4.3 Sites

Sites are points that must be connected via PTP links. A Project may contain two or more
sites.

4.3.1 Inserting New Sites

Identify all sites in the project and obtain their latitude and longitude using the WGS84 frame
of reference. This can be done using tools such as:

GPS during a site survey.

Google Earth: http://earth.google.com. This must be downloaded and installed.

Multimap: http://www.multimap.com/.

4.3.1.1 Importing Sites from Google Earth (.KML)

This is the recommended way to insert sites in the project.

In Google Earth, create a folder, locate the sites using address or zip code, insert
placemarks, add placemarks to the folder, then save the folder as a .kml file.

When a site is located using address or zip code, Google Earth normally inserts
the placemark in the street adjacent to the building. To obtain precise latitude and
longitude, move the placemark to the building where the antenna is mounted.
In PTP LINKPlanner, select File, Import, Points from KML. When import is completed, the
sites can be be accessed from the Sites node in the navigation tree (4.1.3).

4.3.1.2 Importing Sites from a .CSV File

This method may be used when the customer has provided the network planner with a .csv
file in the required format (8.3) containing the sites.
In PTP LINKPlanner, select File, Import, Points from csv. When import is completed, the
sites can be be accessed from the Sites node in the navigation tree (4.1.3).

Latitude and longitude in customer supplied .csv files should always be confirmed
using Google Earth or some other tool.

37
4.3.1.3 Manually Inserting Sites

Locate the sites using Google Earth or Multimap. Copy the latitude and longitude of each
site.

To insert the site in PTP LINKPlanner, either select Project, New Site, or click on the New
Site icon:

The New Site page is displayed (Figure 29).

Figure 29 New Site page

Name: Enter the site name.

Maximum Height: The height is entered in the units used in the Options/Preferences page
(feet or meters). This is the maximum height allowed at the site.

Latitude and Longitude: The latitude and longitude must be in a format which can be
understood and must use the WGS84 frame of reference. The following formats are
supported:

+12.34567, 12.34567N or 12.34567E North or East

-12.34567, 12.34567S or 12.34567W South or West

12:34.567N degrees, decimal minutes and point of compass

12:34:56.7N degrees, minutes, decimal seconds and point of compass

WGS84 is used by Google Earth and all GPS equipment but sometimes the GPS is set to
some other frame of reference.

Description: Enter the site description.

38
4.3.2 Displaying the Sites List

When one or more sites have been created, they appear in the Sites list (Figure 30). To
display this list, select the Sites node in the navigation tree. The Sites list is displayed in the
right hand panel. Use click and drag on the column headings to reorder the columns. To
select which fields are displayed in the list, right-click on the heading row.

Figure 30 - Sites List

4.3.3 Viewing and Updating Sites

Existing sites can be opened in the following ways:

Single-click the site node in the navigation tree.

Double-click on the site in the Sites list.

The Site page is displayed.

4.3.3.1 Site Details

View and update the Name, Maximum Height, Latitude, Longitude and Description (Figure
31). See 4.3.1.3 for field definitions.

Figure 31 Details in Site Page

39
4.3.3.2 Links to Site

This is a list of links that have been defined between this site and other sites in the project
(Figure 32). To add or remove columns to the list, right click and tick or untick columns.
Double-click on a link to open the Links page.

Figure 32 - Links in Site Page

4.3.3.3 Site Links Graph

This is a map of the sites and links in the project (Figure 33).

Figure 33 - Links Graph in Site Page

40
4.4 Links

4.4.1 Inserting New Links

Having defined the sites within the Project, the user can define the Links between them. To
create a new Link, either select Project, New Link, or click on the New Link icon:

The New Link page is displayed (Figure 34).

Figure 34 - New Link Page

Two lists of the available sites to be connected are displayed. The search fields narrow the choice
when there is a large number. Select one site from each list and hit OK. The link is made between
those two locations and the Link page is displayed.

41
4.4.2 Displaying the Links List

When one or more links have been created, they appear in the Links list (Figure 35). To
display this list, select the Links node in the navigation tree. The links list is displayed in the
right hand panel. Use click and drag on the column headings to reorder the columns. To
select which fields are displayed in the list, right-click on the heading row.

Figure 35 - Links List

4.4.3 Viewing and Updating Links

Existing links can be opened in the following ways:

Click on the link node in the navigation tree.

Double-click on the link in the Links list.

The Link page is displayed (4.5).

42
4.4.4 Obtaining Link Profiles

To obtain profiles of the terrain between the two end points of each link, select Project, Get
Profiles. The Request Profiles page is displayed (Figure 36).

Figure 36 - Request Profiles Page

The links that do not yet have profiles are ticked by default. The links that already have
profiles are unticked by default, but the user may tick them if the profiles require update.

Click OK to obtain profiles. PTP LINKPlanner automatically sends the requests to the
Motorola PTP Path Profiler.

If a URL error is displayed in response to the PTP Path Profiler request, visit the
Options/Preferences page (4.1.1) and if necessary, update the HTTP Proxy settings.

In response, Path Profiler sends an email to the users mailbox. Open the email, double-click
on the attached .dat file(s) and click Open.

43
The Import page (Figure 37) is displayed.

Figure 37 - Import .dat Page

Click OK to import the profile. If there is an existing profile for this link, the overwrite warning
must be checked to delete the old profile.

44
4.4.5 Updating Profiles with Obstructions

PTP Path Profiler does not include any path obstructions such as buildings or trees (although
large buildings may have been included in the profiles as part of the terrain). Therefore, it is
necessary to revisit each link path and check for the presence of obstructions. Then, the
obstruction data must be entered into the link profile.

4.4.5.1 Identifying Obstructions

Obstructions in the path (such as trees or unidentified buildings) may affect link performance if
they enter the Fresnel zone and alter the slope. It is therefore important to identify these
obstructions and add them to path profiles, especially near the high points of the path.

If this cannot be done by walking the high points of the path with a GPS, the link can be
viewed in Google Earth aerial photographs (if available), identifying obstructions, and
estimating their heights and positions. To do this, open the link in PTP LINKPlanner and click

on the Google Earth toolbar icon . When the aerial photgraph is displayed in Google
Earth, use the Ruler tool to find the positions of obstructions (Figure 38). The labels Hp1
and Hp3 identify the high points on the path.

Figure 38 - Google Earth Aerial Photograph with High Points and Ruler Tool

45
4.4.5.2 Editing the Profile

When the link profile .dat file has been imported, select the link in the navigation tree to view
the Link Page (4.5). The Profile visualization chart (Figure 39) does not yet include obstructions.

Figure 39 - Profile Visualization Chart

Double-click on the Profile visualization chart. The Profile Editor page is displayed (Figure
40). Enter or update the Range or Obstruction height as required.

For example, if a 4 metre high tree has been identified at Range 0.501 km, enter 4.0 in the
Obstruction column at Range 0.501.

46
 Figure 40 - Profile Editor

The Profile is updated to represent the tree as a green point above the terrain (Figure 41).

Figure 41 Profile updated with tree obstruction (in green)

47
4.5 Evaluating Link Performance

The Link page allows the user to evaluate the performance of a Link by selecting different
combinations of the variables that affect performance, such as band, region, equipment,
antenna and height. The results can be reviewed in the Performance Summary and
Performance Details sections.

Before using this page, ensure that the following requirements are defined for both ends of
the link:

Mean Throughput Required (Mbps).

Minimum Throughput Required (Mbps).

Minimum Throughput Availability Required (%).

The Link page includes the following features:

Each section begins with a blue title bar. Click on this bar to open or close the
section.

The numeric data entry fields can be incremented or decremented in steps by using
the up and down arrow keys. The user can then evaluate the impact of step changes
on link performance.

If a field is highlighted in pink, this means that its value is out of the permitted range.

4.5.1 Link Description

Enter the Name and Description of this link (Figure 42).

Figure 42 Link Description

48
4.5.2 Equipment

Select the equipment, license and optimisation method for this link (Figure 43).

Figure 43 - Equipment

Band: Select the frequency band used by the PTP bridge.

License: Select the license that applies to the region in which the link is located.

Product: This is set automatically, depending on Band: PTP54500 (for 5.4GHz), or

PTP58500 (for 5.8GHz).

Bandwidth: This is fixed at 15MHz.

Optimisation: Select the optimisation for the link, either for IP Traffic or TDM Traffic. If TDM has
been enabled, the link will automatically be optimised for TDM traffic/latency.

Symmetry: The link operation for the PTP500 is fixed as Symmetric.

Master: Select which site is the master.

49
4.5.3 Profile

This is a visualization of the path between the two sites (Figure 44).

Figure 44 - Profile with tree

In this example, a 4m high tree at 0.5km enters the Fresnel zone and alters the slope.

Colour code used in the profile:

Brown: terrain.

Green: obstructions (such as trees or buildings). These can be updated as described

in 4.4.5 Updating Profiles with Obstructions.

Red: line of site from the antennas to the largest obstruction (called slope).

Blue: the Fresnel zone.

Grey: the profile worst case which occurs up to 0.01% of the time. Sometimes known
as Worst Earth curvature (Ke).
To update the profile with obstructions, click on the Google Earth toolbar icon:

. For more information, see 4.4.5.

50
4.5.4 Configuration of Local and Remote Ends

Use this to evaluate different antenna configurations at each end of the link (Figure 45).

Figure 45 - Configuration of Local and Remote ends (local shown)

Enter data about the antenna, transmission power and interference density (Local and
Remote ends). In response, the Performance Summary section is updated automatically and the
user can see the effect upon the Mean Throughput, Minimum Throughput and Availability. The
Local and Remote ends are each divided into three parts:

Data that affects both transmission and reception: Antenna, Diversity Spacing,
Antenna Height and Cable Loss.

Data that affects transmission only: Maximum EIRP, Maximum Power.

Data that affects reception only: Interference Density.

Antenna: Select the required antenna from the drop-down list, or select Other and enter the
details in the User Defined Antenna page.

Antenna Height (meters): This is the height of the antenna above ground level (AGL), not the
height above the building on which it is mounted. The Profile visualization is automatically updated
in response to changes in Antenna Height.

Diversity Spacing (meters): This field is only displayed if a single polar external antenna is
selected.

51
Cable Loss (dB): This field is not displayed for INTEGRATED antennas. If a non-integrated
antenna is used, power may be lost in the cable connection between the radio and the
antenna, therefore the Cable Loss must be estimated. To enter Cable Loss:

Either: enter the estimated loss in the dB field.

Or: tick the Calculate box, select the type of cable that connects the radio to the
antenna (LMR400, LMR500 or LMR600), and enter the length. In response, the dB
field is automatically updated.

Maximum EIRP (dBm): The maximum available Equivalent Isotropic Radiated Power. The
default value is determined by the Band, License, Product and Antenna. If a lower user-defined
limit is required, tick the User Limit box and enter the value. In response, the default Maximum
EIRP is automatically reset to the User Limit.

Maximum Power (dBm): The maximum available transmission power. The default value is
determined by the Band, License, Product and Antenna. If a lower user-defined limit is required,
tick the User Limit box and enter the value. In response, the default Maximum Power is
automatically reset to the User Limit.

Interference Density (dBm/15MHz): This is the amount of site noise in the 15MHz channel
bandwidth, expected at the antenna connector. This noise is assumed to be a constant power
added to the thermal noise of the front end of the wireless. If mean power measurements from
DFS are available then a close approximation is to use this value, which will then be taken into
account, but this is only possible after link set up. To enter Interference density, tick the box and
update the default value.

52
4.5.5 Performance Summary

This shows how well the link will perform in response to the selected combination of the
variables, such as band, region, equipment, antenna and height (Figure 46). It shows receive
performance at the Local and Remote ends of the link.

Figure 46 - Performance Summary

4.5.5.1 Link Loss Summary

This summary highlights the Free Space Path Loss component and the Excess Path Loss based
upon the diffraction loss over the obstacles that cut the Fresnel zone number 0.5. The Total Path
Loss and System Gain Margin are also given.

Aggregate Throughput (dB): The sum of the Mean Throughput Predicted at the Local and
Remote ends.

Link Availability (dB): The average of the Receive Reliability percentages at the Local and
Remote ends.

System Gain Margin (dB): The gain margin of the link in dB.

Free Space Path Loss (dB): The loss incurred along a line-of-sight path between the two end
points of the radio link, based upon the diffraction loss over the obstacles that cut the Fresnel zone
number 0.5.

Excess Path Loss (dB): The loss incurred due to obstacles between the two end points of the
radio link, based upon the diffraction loss over the obstacles that cut the Fresnel zone number 0.5.

Total Path Loss (dB): The sum of Free Space and Excess Path Loss.

53
4.5.5.2 Receive Performance at Local

This is a prediction of the receive data rate and reliability at the local end of the link, based on
the equipment and performance data entered. The user must enter the required data rate and
reliability for comparison with the predicted data. This allows the user to decide whether or
not the performance of the link will be acceptable.

Mean Throughput Predicted (Mbps): Calculated from the data entered.

Mean Throughput Required (Mbps): Enter the required mean data rate.

Percentage of Required Throughput: This is the Predicted rate as a percentage of the

Required rate.

Minimum Throughput Required (Mbps): Enter the required minimum data rate.

Minimum Throughput Availability Required (%): Enter the required minimum reliability of
the link. This is the percentage of the time in which the link is required to meet or exceed the
Minimum Throughput Required.

Minimum Throughput Availability Predicted (%): This is the percentage of the time in
which the link is predicted to meet or exceed the Minimum Throughput Required.

If the predicted data rates fall below the required rates, they are displayed in red. If they meet
or exceed the required rates, they are displayed in green. In this example, at the Local end
(Figure 46), the Mean Throughput Predicted is displayed in red because it is below the rate
required, but the Receive Reliability is displayed in green because it exceeds the
requirement.

4.5.5.3 Receive Performance at Remote

This is a prediction of the receive data rate and reliability at the remote end of the link. The
fields are defined in 4.5.5.2

54
4.5.6 Performance Details

This section contains more detail about the predicted performance of the link (Figure 47).

Figure 47 - Performance Details

Mode: The modulation technique used.

Code Rate: The code rate for the specified Mode.

Payloads: Indicates whether the payload mode is Single or Dual.

Max. Aggregate User Throughput (Mbps): The maximum aggregate throughput achievable
(sum of both directions). This is automatically adjusted for the range of the link being studied.

Max. User Throughput in Either Direction (Mbps): The maximum user throughput
achievable in a single direction.

Fade Margin to Local (dB): The margin available to the Local end in the specified Mode.

Throughput Availability to Local (%): The percentage of time that the data throughput rate
shown for the Local end will be available.

Fade Margin to Remote (dB): The margin available to the Remote end in the specified
Mode.

Throughput Availability to Remote (%): The percentage of time that the data throughput
rate shown for the Remote end will be available.

55
4.5.7 Flags

Use this section to add one or more flags to indicate the status of the link (Figure 48). For
example, enter Backbone, Spur or Unused. Each Flag value is displayed as a column in
the Links report.

Figure 48 - Flags

56
4.6 Exporting Data

4.6.1 Links (CSV)

The link details can be viewed in Excel. Select the Links node in the navigation tree and click
on the View in Spreadsheet toolbar icon:

Link details can be exported to a CSV file by selecting File, Export, Links (csv). The CSV
file can then be incorporated into a spreadsheet to enable further analysis and costing of the
project.

4.6.2 Sites (CSV)

Details of all sites can be exported to a CSV file by selecting File, Export, Sites (csv).

4.6.3 Site (CSV)

Details of a single site can be exported to a CSV file by selecting File, Export, Site (csv).

4.6.4 Google Earth (KML)

The site details can be exported to a KML file by selecting File, Export, Google Earth (kml).
The KML file can then be used to view the project sites in Google Earth. This can also be
reviewed quickly using the toolbar button.

57
4.7 Creating Reports

Reports can be created in HTML format for the currently open and selected project.

Reports can be previewed using the Preview Report toolbar icon:

4.7.1 Project (one page or multipage)

Project reports consist of project and link details, exported in HTML format.

To create a project report in a single HTML file, select File, Reports, Project (one
page).

To create a project report in multiple HTML files, select File, Reports, Project
(multipage). The report is saved as a set of HTML files, one for project details and
one for each link.

Project details consist of: Customer Information, Prepared By, Network Map and Links list. By
clicking on the hyperlinks in the Links List, the report viewer can navigate to the Links reports.

Link details consist of: Summary, Installation Notes, Local Site, Remote Site, Link Throughput
& Availability, Required User Throughput, Path Profile, Regulatory Conditions and Prepared
By.

4.7.2 Links Table

To export the project links table to a single HTML file, select File, Reports, Links Table.

4.7.3 Link

To create a link details report for a single link, select the link in the navigation tree and select
File, Reports, Link. The report is saved as a single HTML file, with link details as listed
above (4.7.1).

4.7.4 Site

To create a report for a single site, select the site in the navigation tree and select File,
Reports, Site. The report is saved as a single HTML file.

58
5 Path Loss Considerations
The path loss is the amount of attenuation the radio signal undergoes between the two ends
of the link. The path loss comprises the sum of the attenuation of the path if there were no
obstacles in the way (Free Space Path Loss) and the attenuation caused by obstacles
(Excess Path Loss). It is also necessary to consider a margin to allow for possible fading of
the radio signal (Fade Margin), and an allowance for the seasonal effects of foliage growth, to
achieve a reliable link. This path loss must be lower than the equipment capability for the data
rate required.
LFreeSpace + LExcess + LFade + LSeason < LCapability
Where
LFreeSpace = Free Space Path Loss see section 2.1 dB
LExcess = Excess Path Loss see section 2.2 dB
LFade = Fade Margin Requirement see section 2.3 dB
LSeason = Seasonal Fading dB
LCapability = Equipment Capability dB

Equation 1 - Path Loss

Adaptive modulation will ensure that the highest throughput that can be achieved
instantaneously will be obtained taking account of propagation and interference. For more
information about the architecture and specification of the PTP 500 series bridge, refer to
PHN-1115 PTP 500 Series User Guide.

The calculation given in Equation 1 needs to be performed to judge whether a particular link
can be installed. This calculation is performed by the LINKPlanner. When the link has been
installed web pages provide information about the link loss currently measured by the
equipment both instantaneously and averaged.

59
5.1 Free Space Path Loss

The Free Space Path Loss is the loss incurred along a line-of-sight path between the two end
points of the radio link. Figure 1 gives a graph of the value in dB by range at the frequency used by
PTP500 bridges .

Figure 49 - Free Space Path Loss at 5.8GHz

5.2 Excess Path Loss

The Excess Path Loss is the loss incurred due to obstacles between the two end points of the
radio link. This loss is best calculated using the PTP LINKPlanner. Trees and foliage create a
number of problems;

they are often not marked on the path profiles producing optimistic results,

they are not completely solid producing pessimistic results,

they are responsible for seasonal variation.

It is recommended that they be treated as solid objects thus giving worst case results, and
when the link is installed the mean path loss indicated should be given an allowance for the
seasonal variation that will occur.

60
5.2.1 Fresnel Zone

There is a theoretical area around the line-of-sight of an antenna, called the Fresnel Zone.
Objects that penetrate the Fresnel Zone block some of the signal travelling from transmitter to
receiver, causing the path loss to increase. The Fresnel radius at a point along the path is
defined as follows:

in meters where:

d1 = distance from one end in meters

d2 = distance from the other end in meters

Equation 2 - Fresnel Zone Radius

61
 Figure 50 - Fresnel Radius for Zone 0.5

The two graphs in Figure 50 give the radius of the mid point of a link and also give the radius
of any link near one end. Thus for a link longer than 1 km (0.6 mi), the radius of the Fresnel
Zone at 100 meters (330 ft) is 1.7 meters (5.6 ft). This is useful to know since the objects
nearest the ends of the link tend to have a greater influence on the link losses than objects at
the middle of the link. For a thorough understanding of the Fresnel Zone refer to ITU-R
P.526.9.

5.3 Fade Margin

A Fade Margin needs to be applied to the link budget to take into account changes in the
radio path caused by changes in objects surrounding or in the path, e.g. moving objects such
as traffic or the changes in foliage brought on by seasonal change. The Fade Margin for
NLoS links used in the calculation is a function of excess path loss, and is taken from Figure
51. The Fade Margin for LoS links is a function of location, path length, antenna heights, and
spatial diversity, and it is computed using ITU-R P.530-10. The estimation tool adds together the
probabilities for the NLoS fading and the LoS fading.

62
 Figure 51 - Fade Margin vs Excess Path Loss for 99.99% Link Availability

5.4 Maximum Path Loss

The Maximum Path Loss is the total path attenuation that the system can withstand and still
maintain 99.99% availability. Due to different spectrum licensing conditions in different
countries the Maximum Path Loss varies from country to country due to allowable output
power differences. Table 1, Table 2 and Table 3 give the maximum loss that the equipment
can withstand in each mode when deployed in a region that uses a power of 25dBm.
Deployment considerations may limit the maximum power which is used. An example is given
in the Application Note: How to Deploy PTP400 Bridges with Canopy available from the
Motorola Web site. Also, there may be local interference sources from other users of the 5.8
GHz band.

5.5 Paths Over Sea or Very Flat Ground

Paths over the sea are subject to a special problem due to the very strong reflection from the
water. This reflection can add an anti-phase signal to the direct wave and cancel it out
completely. This may not happen all of the time because the effective curvature of the earth
changes depending upon the temperature gradient in the atmosphere. This gradient can
change and in certain circumstances causes the signal to travel a long way in ducts. Figure 4
illustrates the problem and the solution using a PTP500 bridge. The background of the
diagram is shaded to illustrate the changing density and therefore refractive index. The upper
antennas are in a signal inversion.

63
 Figure 52 - Propagation Over The Sea

The signals pass from one antenna to the other through two paths. One path is the direct path
and the other is reflected from the sea. The mean path loss of the two components is almost
identical. The graph adjacent to the mast illustrates the signal level that will occur as an
antenna is moved vertically on the mast. In this case the x-axis illustrates the amplitude
received while the y-axis illustrates the height.

The polarization selected for the antennas are single V and H polarization on the left and a
dual polarized antenna on the right. The two graphs on the right illustrate the signal received
on each polarization while on the left the individual antennas will receive the same signal level
independent of polarization but instead will only depend upon the height.

There is an optimum vertical spacing of the two antennas on the left which is found from the
geometry of the two paths. The important parameters are the length of the path, the height of
the right single antenna and to a lesser extent the height of the pair of antennas on the left.
An allowance should normally be made for the apparent height of the middle of the path due
to the mean radio curvature of the earth (4/3).

64
6 PTP500 Equipment Features
There are some specific features of the PTP500 equipment which ensure that the products
work as reliably as possible in LoS and NLoS environments. These are

Large System Budget for long range LoS or deep penetration in NLoS Applications.

Multiple-Input Multiple-Output (MIMO) to enable operation with reduced allowance for

fade margin. In NLoS links this is effective using the integrated antenna, and in long
range LoS links this is most effective using separated antennas at one end of the link.

Adaptive Modulation to ensure that the fastest instantaneous data rate is achieved in
varying conditions.

Use of a wide range of external antennas for difficult applications.

Automatic Frequency Management to ensure that the optimum frequency is being

used for communications, depending upon interference.

Comprehensive measurements to ensure that a link will remain reliable after

installation.

65
7 Path Profiles
The accuracy of the results depends upon obtaining accurate path data. In the US this data is
readily available from recent 1 arc second data (20m) obtained by NASA. In the rest of the world
30 arc second data (500m) is freely available but NASA is gradually providing 3 arc second data
(50m) for the world between Latitudes 60 north and 60 south. (See section 9 SRTM Technical
Guide). The LINKPlanner is also able to import from a number of other data sources. Even with
accurate path data, the losses over certain objects depend upon the curvature of the top of those
objects. Nevertheless the tool gives a good idea of the performance to be expected, and by doing
a what/if analysis, helps the user to understand the concept of non-line-of-sight.

In order to obtain an accurate link estimate where the path impinges on the Fresnel zone an
accurate height profile of the path is required. In some parts of the world this path profile can
be obtained from other propagation prediction packages such as MicroPath, PathLoss, ATDI
ICS Telecom, Softwright TAP and Radio Mobile.

7.1 PTP Path Profiler

Motorola has produced the web based utility PTP Path Priofiler (Figure 53) that creates path
profiles, which can be directly imported into the PTP LINKPlanner:

http://motorola2.motowi4solutions.com/support/ptp/pathprofile.php

The file output by PTP Path Profiler is complete in the sense that it includes the
Latitude and Longitude. Most of the imports from other software do not address this
problem and thus it is important to correct the Latitude and Longitude in the PTP
LINKPlanner for translated files.

Prior to use it will be necessary to have:

The latitude and longitude of the local and remote ends of the wireless link in decimal
format to WGS 84.

An email address to which an email containing the path profile files can be delivered.

The heights above ground level of the local and remote ends of the link.

A filename that is used to name the path profile files that are returned via email.

Contact information including name, company and telephone number.

66
Location can be entered in a number of new formats in addition to the decimal format. These
are:

'ddd:mm:ss.sP' eg. 50:33:20.6N,

'ddd:mm.mmmP' eg. 50:33.33.9N, and

'ddd.dddddP' eg 50.55345N.

The Web site requires input of Height and Range units. These are used for the PTP
LINKPlanners use of this path. The Antenna Heights are referenced to ground level, they are
adjustable in the PTP LINKPlanner. The number of points divided by the range of the link gives the
resolution along the path of the link. The link name is displayed on the graphical display of the PTP
LINKPlanner. The Filename has .dat appended to it. The Contact Name enables Motorola to
know who is requesting path profiles. The Company Name and Phone is for similar purposes. The
Email address is the site where the path profile will be delivered usually in a few minutes after
pressing Send Form.

Checks that should be made on loading the path profile are:

Is the ground height at each end of the link what is given by the tool?

Are any over water segments of the path accurate? Inaccuracies in these are caused
by the method of survey, which is radar on board a satellite. The ground return is
dispersive in angle ensuring that some power goes back to the satellite. A water
return in calm conditions can be reflected in one direction away from the satellite,
which introduces errors, which may be very large.

There are three data sources used in these profiles. The lowest resolution is global and is in
30 arc second steps (900 meters) using 1 meter vertical resolution. The middle resolution
covers most of the land area between 61 degrees North and 61 degrees South, it has 3 arc
second resolution steps (90 meters) using 1 meter vertical resolution. The highest resolution
is for the United States only, it has 1 arc second resolution steps and also has 1 meter
vertical resolution.

The vertical accuracy is claimed by NASA to be 10 meters RMS. It is noticeable that the
middle resolution has less noise than the highest resolution and yet it comes from the same
radar scans (February 2000 Shuttle Radar Topography Mission SRTM). This is because each
data point is an average of 9 points from the highest resolution. The low resolution data was
obtained from many different sources.

See Section 9 for a technical guide to SRTM which acknowledges NASA and the University
of Marylands work.

67
Figure 53 - PTP Path Profiler web page

68
7.2 Path Profile E-mail

After submitting the link parameters to the path profiler server, the server generates detailed
path profile data. The data is returned via an email. The email has three files attached:

DAT file: The DAT file is a Motorola proprietary format file suitable for loading into
the PTP LINKPlanner.

PDF file: This file is a graphical representation of the link profile, useful for a quick
visualization of the path.

GPX: The file enables checking the path using a GPS, Expert GPS or Terrabrowser
software.

KML: KML, or Keyhole Markup Language, is an XML grammar and file format for
modeling and storing geographic features such as points, lines, images, and
polygons for display in Google Earth.

69
8 Import File Formats
The PTP LINKPlanner can import profile data files in a number of common formats. The
supported formats are detailed in the subsections below.

8.1 Path from Hydra - no Site Names (*.pth)

Format of the path file exported by Motorola Hydra (without site names):
40.047845833333334 -75.175095277777771
40.042207222222224 -75.168060277777784
50 TxHt(Meters)
8 RxHt(Meters)
5734 Freq(Mhz)
0
0 95 0 0
0.76553904027639119 95 0 15
1.5310780805527824 95 0 15
2.2966171208291732 95 0 150.60,1712.7,,0.00

8.2 Path from Hydra - with Site Names (*.pth)

Format of the path file exported by Motorola Hydra (with site names):
SiteNames
Big House
Garage
40.047845833333334 -75.175095277777771
40.042207222222224 -75.168060277777784
50 TxHt(Meters)
8 RxHt(Meters)
5734 Freq(Mhz)
0
0 95 0 0
0.76553904027639119 95 0 15
1.5310780805527824 95 0 15
2.2966171208291732 95 0 15

8.3 Points from Comma Delimited File (*.csv)

Points (sites) can be defined in a CSV (comma separated variable) file, created by the user
using Excel or a text editor. The first row contains titles. For example:

Name, Latitude, Longitude, Maximum Height, Descripion

Place1, 50.371N, 3.523W, 200, Desc of place 1
Place2, 50.384N, 3.525W, 100, Desc of place 2

70
9 SRTM Technical Guide

71
72
10 Legal Notices
10.1 Motorola Inc. End User License Agreement

In connection with Motorolas 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.

10.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 Motorolas MOTOwi4 fixed wireless broadband devices for which the
Software and Documentation is licensed for use.

10.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 3 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.

10.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.

73
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.
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 (e.g., 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.

74
10.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 Motorolas 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 Motorolas 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.

10.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.
1. 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.

75
10.1.6 Right to Use Motorolas Name

Except as required in 10.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.

10.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. Motorolas 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.

10.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/.
1. 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.

10.1.9 Maintenance

Except as provided above, Motorola is not responsible for maintenance or field service of the
Software under this Agreement.

10.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

76
 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.

10.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.

10.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.

10.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

77
 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.

10.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.

10.1.15 Assignment

This agreement may not be assigned by you without Motorolas prior written consent.

10.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.

10.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.

78
10.2 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.

Follow the URLs quoted below to verify the full text of Third Party software licenses.

1. Python License (http://www.python.org/psf/license/):

The Python license imposes very few restrictions on what you can do with Python. Most
of the source code is copyrighted by the Python Software Foundation (PSF). A few files
have a different copyright owner, but the same license applies to all of them.

In layman's language, here are the primary features of Python's license. The following
descriptions are not legal advice; read the full text of the license and consult qualified
professional counsel for an interpretation of the license terms as they apply to you.

Python is absolutely free, even for commercial use (including resale). You can sell a
product written in Python or a product that embeds the Python interpreter. No
licensing fees need to be paid for such usage.

The Open Source Initiative has certified the Python license as Open Source, and
includes it on their list of open source licenses.

There is no GPL-like copyleft; restriction. Distributing binary-only versions of

Python, modified or not, is allowed. There is no requirement to release any of your
source code. You can also write extension modules for Python and provide them only
in binary form.

However, the Python license is compatible with the GPL, according to the Free
Software Foundation.

You cannot remove the PSF's copyright notice from either the source code or the
resulting binary.

79
2. wxWidgets (http://www.wxwidgets.org/about/newlicen.htm):

wxWidgets is currently licensed under the "wxWindows Licence" pending approval of the
"wxWidgets Licence" which will be identical apart from the name.

The wxWindows Licence is essentially the L-GPL (Library General Public Licence), with
an exception stating that derived works in binary form may be distributed on the user's
own terms. This is a solution that satisfies those who wish to produce GPL'ed software
using wxWidgets, and also those producing proprietary software.

Participants in the discussion that led to this decision include the folk from Abisource,
Robert Roebling, Julian Smart, Markus Fleck, Karsten Ballueder, and some advice from
Richard Stallman. Richard has confirmed that the new licence is compatible with GPL'ed
applications. However, there are no significant restrictions on proprietary applications.

The wxWindows Licence has been approved by the Open Source Initiative, and you can
find the licence on their site here.

In August 2005, an ambiguity in Clause 2 was removed (replaced "the user's" with "your")
and the version bumped to 3.1.

3. Genshi (http://genshi.edgewall.org/wiki/License):

Copyright 2006-2007 Edgewall Software. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3. 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,

80
 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.

4. FormEncode (http://pypi.python.org/pypi/FormEncode). Covered by the Python license.

5. Python for Windows Extensions (http://sourceforge.net/projects/pywin32). Covered by

the Python license.

6. matplotlib (http://matplotlib.sourceforge.net/license.html):

LICENSE AGREEMENT FOR MATPLOTLIB 0.91.2svn:

1. This LICENSE AGREEMENT is between the John D. Hunter ("JDH"),

and the Individual or Organization ("Licensee") accessing and
otherwise using matplotlib software in source or binary form and
its associated documentation.

2. Subject to the terms and conditions of this License Agreement,

JDH hereby grants Licensee a nonexclusive, royalty-free, world-
wide license to reproduce, analyze, test, perform and/or display
publicly, prepare derivative works, distribute, and otherwise use
matplotlib 0.91.2svn alone or in any derivative version, provided,
however, that JDH's License Agreement and JDH's notice of
copyright, i.e., "Copyright (c) 2002-2004 John D. Hunter; All
Rights Reserved" are retained in matplotlib 0.91.2svn alone or in
any derivative version prepared by Licensee.

3. In the event Licensee prepares a derivative work that is based

on or incorporates matplotlib 0.91.2svn or any part thereof, and
wants to make the derivative work available to others as provided
herein, then Licensee hereby agrees to include in any such work a
brief summary of the changes made to matplotlib 0.91.2svn.

4. JDH is making matplotlib 0.91.2svn available to Licensee on an

"AS IS" basis. JDH MAKES NO REPRESENTATIONS OR WARRANTIES,
EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, JDH
MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF
MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE
USE OF MATPLOTLIB 0.91.2svn WILL NOT INFRINGE ANY THIRD PARTY
RIGHTS.

5. JDH SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF

MATPLOTLIB 0.91.2svn FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL
DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR
OTHERWISE USING MATPLOTLIB 0.91.2svn, OR ANY DERIVATIVE THEREOF,
EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

81
 6. This License Agreement will automatically terminate upon a
material breach of its terms and conditions.

7. Nothing in this License Agreement shall be deemed to create any

relationship of agency, partnership, or joint venture between JDH
and Licensee. This License Agreement does not grant permission to
use JDH trademarks or trade name in a trademark sense to endorse
or promote products or services of Licensee, or any third party.

8. By copying, installing or otherwise using matplotlib 0.91.2svn,

Licensee agrees to be bound by the terms and conditions of this
License Agreement.

7. NumPy (http://pypi.python.org/pypi/numpy). Covered by the Python license.

10.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 MOTOROLAS LIABILITY EXCEED
THE AMOUNT YOU PAID FOR THE PRODUCT.

82
11 Glossary
AGL Above Ground Level
AMSL Above Mean Sea Level
Advanced Topographic Development & Images
ATDI
Ltd.
BPSK Binary Phase Shift Keying
CD Compact Disc
CSV Comma Separated Variables
DFS Dynamic Frequency Selection
EIRP Equivalent Isotropic Radiated Power
ETSI European Telecommunications Standards Institute
FCC Federal Communications Commission
FEC Forward Error Correction
ITU International Telecommunications Union
KML Keyhole Markup Language
LoS Line-of-Sight
MIMO Multiple-Input Multiple-Output
NLoS non-Line-of-Sight
PTP Point-To-Point
SRTM Shuttle Radar Topography Mission
TDD Time Division Duplex
TDM Time Division Multiplexing

83
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

84
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.