Obstructions: Linkplanner User Guide, Release 4.8.2

LINKPlanner User Guide, Release 4.8.
Figure 3.42: Profile Visualization Chart
Obstructions
Double-click on the Profile visualization chart. The Profile Editor page is
displayed. Enter or update the Range or Obstruction height as required. For
example, enter a 4 meter high Obstruction at Range 0.501 km and a 3.5 meter
high Obstruction at Range 0.678 km.
If necessary, make allowances for forests and tall buildings:
An obstruction of roughly constant height (for example a forest) may extend
over two or more points. To enter such an obstruction, select all the affected
Obstruction Height cells, type a value and press Enter. For example, if a
forest with 12 m high trees extends from Range 1 km to 1.2 km, select the
Obstruction Height cells for this range, type 12 and press Enter.
If a tall building partially obstructs the Fresnel zone by cutting vertically into
one side, treat it as though it cuts horizontally into the bottom of the Fresnel
zone. For example, if it extends 3 meters into the right hand side of the zone,
enter it as a 3 m high obstruction.
Profiles 91
LINKPlanner User Guide, Release 4.8.2
Figure 3.43: Profile Editor
The Profile is updated to represent the trees as green points above the terrain.
Figure 3.44: Profile Updated With Tree Obstructions (in green)
Adding new points

If you would like to add an obstruction in between two of the existing profile
points, you can add a new point using the Add Point button.
92 Chapter 3. Using LINKPlanner

Figure 3.45: Adding a Profile Point
You need to specify the range along the path, the terrain height at that point, and
the obstruction height. For either of the heights, you can press the Estimate
height button to enter a height based on the points either side of the new one.
Deleting points
You can remove points from the profile by selecting them and pressing the
Delete Points button. Any points except the first and last may be deleted.
Editing multiple points

Some types of obstruction, for example forests, may extend for some distance
along the path. These can be represented in the profile by editing multiple points.
To set the same height for multiple points, select those points and type the new
height. When you press Return, that height will be entered for all those points.
To adjust the heights for multiple points so that there is a constant gradient, set
the heights at either end of the range, then select the range and click the Straight
Line button .
Profiles 93
Figure 3.46: Setting a Constant Gradient
Copy a Path Profile

There are two methods for copying a path profile:
Right-click on the Profile Visualization Chart and choose Copy from the
pop-up menu
Open the Profile Editor and click
Pasting a Path Profile

There are two methods for pasting a path profile:
Right-click on the Profile Visualization Chart and choose Paste from the
pop-up menu
Open the Profile Editor and click
LINKPlanner will use the units that are defined in the header row of the
path profile data when a profile is pasted. If the header row is missing or
if the units are not recognized then the preferred units will be used.

Figure 3.47: Path Profile Units
Editing a Profile as a Spreadsheet

Open the Profile Editor and click . Once you have made the appropriate
changes to the profile, copy the information and paste it back into LINKPlanner
(see Pasting a Path Profile).
Link Profile Adjustment Examples
These examples show how Cambium link planners use a map, Google Earth and
surveys to adjust link profiles.
The original path profile for the point-to-point link from Addislade Farm to Yelland
Cross Farm is built using the PTP Path Profiler data:
Figure 3.48: Original path profile
We verify the link ends and the high points as described in the following examples:
Verifying a Link End Using a Map and Google Earth
Verifying a Link End Using a Survey
Verifying a High Point Using a Map
Profiles 95
Verifying a High Point Using a Survey

These methods are applied to both link ends and to all high points in the link path.
The resulting path profile is shown here:
Figure 3.49: Adjusted path profile
Verifying a Link End Using a Map and Google Earth
This is an example to show how Cambium link planners use a map and Google
Earth(TM) to estimate the height of the terrain and obstructions near one end of a
test link. We use the following aids:
Path Profiler data imported into LINKPlanner.
LINKPlanner, open at the Link Profile and Profile Editor.
An accurate topographic map with contours at 10m intervals.
The Google Earth aerial photograph zoomed in on the end of the link.
1. Path Profiler returned the following profile for the start of a link path:

Figure 3.50: Unadjusted profile near antenna site
The first 0.1 km of this link must be examined in more detail.

2. We examine the map of the site:
Figure 3.51: Map of Addislade
The antenna site is just below the 160 m contour, so the path profile height
156.9 m at range 0 km is probably correct. However, the 160 m contour
curves around and crosses the link path at two points in the first 0.1 km of
the link. This means that the path profile height of 157.4 m at range 0.088
km is too low. We estimate that the terrain height at this point is 162 m.
3. We examine the Google Earth air photograph of the link end. This reveals
some potential obstructions:
Profiles 97
Just in front of the antenna - a building and some bushes, estimated

height 6 m.
At 0.1 km from the antenna - a row of trees, estimated height 8 m.
These obstructions and the higher ground are annotated in this Google
Earth photograph:
Figure 3.52: Obstructions and higher ground near Addislade
4. We enter estimates for these obstructions and the higher ground in the
Profile Editor:

Figure 3.53: Profile Updated with Map and Google Earth Results
Our conclusion is that the Fresnel zone may be severely obstructed at this site.
This must be confirmed by conducting a survey, as described in Verifying a Link
End Using a Survey.
Verifying a Link End Using a Survey
This is an example to show how Cambium link planners use a site survey to refine
their estimates of the terrain and obstructions near one end of a test link. This
builds on the previous example Verifying a Link End Using a Map and Google
Earth.
We use the following survey aids:
Map, path profile, Google Earth(TM) aerial photo
Barometric GPS receiver
Clear plastic ruler
Surveyor’s tape measure
Pocket calculator
Binoculars
We follow these steps:
1. We use the barometric GPS receiver to verify terrain height.
Because air pressure may change frequently, the GPS receiver must be
recalibrated near every survey site, at a point with a known altitude. The
Profiles 99
map shows a suitable point for calibration, where the road crosses the 160m
contour near the site, as annotated on this Google Earth photograph:
Figure 3.54: GPS Calibration Point
We calibrate the GPS at this point.

2. We go to the antenna site.
Standing at the foot of the antenna (or of the building on which the antenna
is mounted), we record the terrain height from the GPS: 155m.
3. We estimate the height of the antenna above ground level. The antenna
height used in LINKPlanner is to the center line of the antenna, therefore the
radius of the antenna should be taken into account.
The following height estimation methods can be used:
Method 1: If it is safe (and permissible) to do so, go to the highest accessible
point on the antenna and measure its height using the GPS receiver.
Method 2: If the antenna is on a building, estimate the height of each storey
and count the number of storeys from the ground to the antenna.
Method 3: Ask a colleague to stand under the antenna and estimate the
number of times the colleague’s height would be needed to reach the
antenna height.
Method 4: Stand a measured distance away from the antenna (d2), hold the
ruler at eye level and arms length (d1), measure the height above ground of
the antenna as viewed through the ruler (h1), then calculate the height of
the antenna (h2) using this formula (see illustration):
h2 = h1 * (d2/d1)

Figure 3.55: Using a ruler to estimate height
We record the estimated antenna height: 10m.
This method can also be used to estimate the height of trees and
other potential obstructions. If it is not possible to measure the
distance d2, use the map to estimate it.
4. We examine the potential obstructions and high points that were found on
the air photograph:
A building and some bushes immediately in front of the antenna: The
building proves to be just clear of the link path and is not recorded as an
obstruction. The bushes are on the link path, so we use the ruler method to
estimate and record their height: 5 m.
Higher ground at 0.088 km from the antenna: We go as near to this higher
ground as we can and take the GPS reading: 161.4 m.
A row of trees at 0.1 km from the antenna: This row of trees cuts through the
link path. We identify the tree that is on the path and use the ruler method to
estimate and record its height: 7 m.
These obstructions and the higher ground are annotated in this Google Earth
photograph:
Profiles 101
Figure 3.56: Results of site survey at Addislade
Link planners must allow for the possibility that tree growth or new
buildings may cause new obstructions in the future. If the potential
obstructions are deciduous trees, allow for seasonal changes in
foliage.
5. When we return to the office, we update the profile with these results:
Figure 3.57: Profile updated with site survey results

We now have a more accurate profile of the link end. This will help us to optimize
the link and achieve acceptable data throughput.
Verifying a High Point Using a Map
This is an example to show how Cambium link planners use a map and Google
Earth(TM) to estimate the height of the terrain and obstructions near one high
point of a test link. We use the following aids:
Path Profiler data imported into LINKPlanner.
LINKPlanner, open at the Link Profile and Profile Editor.
An accurate topographic map with contours at 10m intervals.
The Google Earth aerial photograph zoomed in on the high point.
1. Path Profiler returned the following profile for the high point at range 1.061
km:
Figure 3.58: Unadjusted profile near high point
2. We examine the map of the high point. This reveals that the link path is
between the 150 m and 160 m contours:
Profiles 103
Figure 3.59: Map of Hp1
The path profile height 156.5 m at range 1.061 km is probably correct.

However, the map shows a clump of trees surrounding the high point - a
potential obstruction.
3. We enter an estimate of 25 m for the height of the trees in the Profile Editor:
Figure 3.60: Estimated obstruction height near Hp1
Our conclusion is that the Fresnel zone may be severely obstructed at this high
point. This must be confirmed by conducting a high point survey, as described in
Verifying a High Point Using a Survey.
Verifying a High Point Using a Survey
This is an example to show how Cambium link planners use a high point survey to
refine their estimates of the terrain and obstructions near high points. This builds
on the previous example Verifying a High Point Using a Map.
We use the following survey aids:

Map, path profile, Google Earth(TM) aerial photo

Barometric GPS receiver
Clear plastic ruler
Surveyor’s tape measure
Pocket calculator
Binoculars
1. We use the barometric GPS receiver to verify terrain height.
Because air pressure may change frequently, the GPS receiver must be
recalibrated near every high point, at a point with a known altitude. The map
shows a suitable point for calibration, where the road crosses the 150 m
contour near the high point, as annotated on this Google Earth photograph:
Figure 3.61: GPS Calibration Point near Hp1
We calibrate the GPS at this point.

2. We go to the high point (or as near to it as possible) and record the terrain
height from the GPS: 156 m.
3. We go to a place where we can observe the trees from a measured (or
estimated) distance.
We estimate the height of the highest trees in the clump using the ruler
method, as described in Verifying a Link End Using a Survey. We record the
height of the highest trees: 20 m. We also record the height of the trees at
the edge of the clump: 15 m.
4. When we return to the office, we update the profile with these results:
Profiles 105
Figure 3.62: Profile updated with Hp1 survey results
We now have a more accurate profile of the high point. This will help us to
optimize the link and achieve acceptable data throughput.

Bill of Materials for Project
LINKPlanner automatically calculates the Bill of Materials (BOM) from the project
configuration data. The Bill of Materials for the project is split into three sections:
PTP Network BOM - contains an aggregated list of all equipment required
to support the PTP links in the network
PMP Network BOM - contains an aggregated list of all the Hub site and
Access Point equipment required to build the network side of the PMP
network
PMP Subscriber Modules BOM - contains an aggregated list of all the
equipment required for the Subscriber Modules in the PMP network
Optional items, for example the power supply unit and rack mount kit for PTP 800,
can be added to the BOM at the individual link level, see Bill of Materials Optional
Extras . The project BOM contains the list of part numbers and associated
quantities for the complete project (Bill of Materials for Project). It includes all the
main components required to install the project as configured in LINKPlanner,
including antennas, ODUs, modems (PTP 800 or PTP 810 only), upgrade keys,
cabling, lightning protection and GPS sync boxes (if required). It also includes all
optional extras, which have been specified at the link level, cables, accessories
and spares, comsearch, installation & mounting, link protection, long waveguide,
power, security and warranty & support contract.
When designing two links to run in parallel with a single dual polar
antenna at each end, please use the 2+0 Cross-Polar option, otherwise
the BOM lists two dual polar antennas, two waveguides, two RMKs and
two ODUs for each link end. This results in the dual polar antennas
being duplicated in the BOM; only one is required at each end.
To view the project BOM, click “Bill of Materials” from the navigation tree:
Bill of Materials for Project 107

Figure 3.63: Bill of Materials for Project
P/N: The Cambium part number. If the component is not supplied by Cambium,
this is set to ‘(no part number)’.
Description: Description of the components.
Qty: Quantity required.
Notes: Displays information about certain items, such as whether they are
obsolete. This information can be edited at the individual link level.
For instructions on how to view and save the BOM for an individual PTP
link, see Bill of Materials for Link, for an Access Point, see Bill of
Materials for Access Point , for a Subscriber Module, see Bill of Materials
for Subscriber Module .
Viewing & saving the project BOM file
To view the project BOM in Excel, click Export Project to xlsx Workbook , this will
create a multi-sheet Excel workbook with a separate sheet for each of the PTP
Network, PMP Network and PMP Subscriber Modules BOMs and an individual sheet
for the BOM for each PTP Link in the project. The first sheet in the workbook is an

index to each of the individual worksheets. Once in the spreadsheet the file can
be saved as normal.
To create a CSV for an individual section of the BOM, click View in Spreadsheet
while viewing the section of the project BOM required. Once in the spreadsheet
the file can be saved as normal.
All numeric only part numbers consist of 11 digits, if the number

displayed is only 10 digits the part number should start with a zero.
Bill of Materials for Project 109

Project Configuration
The Project Configuration node of the navigation tree contains the following:
PTP Antennas, Access Point Antennas, Subscriber Module Antennas:
View lists of available antennas. For Unlicensed PTP and Subscriber Modules,
create, edit and delete custom antennas. See Available Antennas.
TDD Sync: Manage the global parameters for TDD synchronization of
unlicensed PTP Links and assess the number of interferers. See TDD
Synchronization List.
Custom Fields: Insert, delete and view custom fields for a project, site, link
or end. Custom fields are a way of adding functionality to LINKPlanner.
PTP Link Formatting: Insert, delete and edit link formatting rules for PTP
Links. The rules can be used to control the style and visibility of PTP links
when exporting to different formats or when viewing the PTP Links in the
map. See Formatting Rules.
PMP Formatting: Insert, delete and edit link formatting rules for PMP Links
and Access Points. The rules can be used to control the style and visibility of
PMP links and Access Points when exporting to different formats or when
viewing the PMP Links and Access Points in the map. See Formatting Rules.
PTP Equipment Templates: Create, delete and edit the equipment
templates for PTP Links. The templates are used to set the default
configuration settings for new and existing PTP links. See Equipment
Templates.
PMP Equipment Templates: Create, delete and edit the equipment
templates for PMP Equipment. The templates are used to set the default
configuration settings for new and existing access points and subscriber
modules. See Equipment Templates.
Channel Plans: Create, delete and edit channel plans for PMP networks.
The channel plans are used to allocate frequencies to each Access Point from
a given list and define a color for each frequency which is displayed on the
AP sector in the Offline Map. See Channel Plans.
BOM Estimator: Create, delete and edit BOM Estimates for PTP Links and
PMP Access Networks. Quickly configure different link types and access
networks to determine which items are required in the Bill of Materials. See
BOM Estimator.
Best Server Analysis: Automatically determine which AP is the best option
for all subscriber sites (only available in Windows version). This requires the
access points to be created prior to running. See Best Server Analysis.
Available Antennas
To view the list of available antennas, select the appropriate list from the following
options:
PTP Antennas
Access Point Antennas

Subscriber Module Antennas

The Available PTP Antennas page is displayed in the right hand panel. The column
headings vary slightly between the lists.
Figure 3.64: Available PTP Antennas
If the antenna pattern is stored in LINKPlanner then when the antenna is selected
the Save Antenna Pattern will be highlighted. To save the antenna pattern click
and select the required folder and if necessary adjust the default filename. Not
all antennas have antenna patterns stored within LINKPlanner.
PTP Unlicensed and Subscriber Module Antennas Only
If the required antenna is not in the list, click and enter the details in
the User Defined Antenna page. New antennas can only be added in the
unlicensed PTP band and for Subscriber Modules. At present the licensed PTP
band and Access Points only support Cambium antennas.
To delete a new antenna, click , this feature is only available for new
antennas created by the user.
To edit antenna details, click and change the details in the Edit
Antenna page. This feature only applies to unlicensed PTP band and Subscriber
Module antennas.
TDD Synchronization List
When TDD Syncnronization is enabled for one or more PTP links in the project(as
described in Link Description and Equipment), they appear in the TDD
Synchronization List. To display this list, click the “TDD Sync” node in the
navigation tree.
Project Configuration 111

The list is displayed in the right hand panel. If the TDD Sync node is selected
when none of the links in the project are Sync enabled, the following message is
displayed:
This project has no synchronized links
Use the TDD Sync list to adjust the Maximum Burst Duration and Frame Duration.
Before a data rate can be considered accurate it needs to be valid. If the TDD
synchronization settings are invalid, the link is displayed with a pink background
and Aggregate Throughput is set to zero.
In order to observe both the individual link and the TDD synchronization
parameters together, try opening the TDD Synchronization List in a new
window.
Figure 3.65: TDD Synchronization List
The Maximum Burst Duration and Frame Duration possibilities are affected by the

Bandwidth selected for each link. The number in the brackets for each of the drop
down lists is the number of links NOT satisfied by the value selected:
Maximum Burst Duration: Adjusting this value while reviewing the Burst
Duration in the table will help to give a view on the RF efficiency of the link. If the
Burst Duration in the table is not the same as the Maximum Burst Duration
(indicating poor RF Efficiency) either change the Maximum Burst Duration or
change the bandwidth of the link on the Link page (as described in Link
Description and Equipment).
Frame Duration: Adjusting the frame duration to a large enough value to ensure
that there are no same phase interfering paths is the most probable requirement.
The number of interfering paths may take a few moments to calculate for large
networks and thus the number is obscured by a progress bar during this
recalculation. A larger value for Frame Duration reduces the number of interfering
paths. These interfering paths only refer to the timing considerations and do not
take into account any propagation factors of path length or obstructions.
The TDD Synchronization list can be saved as a CSV or Excel file by selecting View
in Spreadsheet , see TDD Synchronization List.
Custom Fields
Use Custom Fields to add information, e.g. status, to sites, links and ends.
Different types of Custom Fields can be created:
New Project Field - field name and value are displayed in the General
Information section of the Project page, see General Information.
New Network Site Field - field name and value are displayed in the Details
section of the Network Site page, see Details in Site Page and shown in the
Network Sites list.
New Subscriber Site Field - field name and value are displayed in the
Details section of the Subscriber Site page, see Details in Site Page and
shown in the Subscriber Sites list.
New PTP Link Field - field name and value are displayed in the Link
Description section of the PTP link page, see Link Description and shown in
the PTP links list. PTP Link Fields can also be selected as link properties in the
Link Formatting rules, see Formatting Rules.
New PTP End Field - field name and value are displayed in the
Configuration at Each End section of the PTP link page, for each end of the
link, see Link Description and shown in the PTP links list, with separate values
for the left and right ends. PTP End Fields can also be selected as link
properties in the Link Formatting rules, see Formatting Rules.
New Hub Field - field name and value are displayed in the Details section of
the Hub page, see Hub Details and shown in the Hubs list view.
New Access Point Field - field name and value are displayed in the Access
Point Details section of the Access Point page, see Access Point Details and
shown in the Access Point list view.

New Subscriber Module Field - field name and value are displayed in the
Subscriber Module Details section of the Subscriber Module page, see
Subscriber Module Description and shown in the Subscriber Modules list view.
Figure 3.66: New Custom Field Options
Creating a Custom Field
To create a new custom field select one of the above options and the Create
custom field window is displayed.
Figure 3.67: Create Custom Field
Enter a Name and then select the Field Type from the following options:
Text - Field only has one value. Enter the value for the field in the Default
Value box.

Yes/No - Field can take the value of Yes or No. Select Yes or No as the Default
Value.
List - Field will display a list of values. Add or delete items in the list by
selecting “+” or “-”, in the Choices section. Enter the option for the default
value. To change from the default option for a particular location, select
another option from the list, which will then be highlighted, see Custom Field
List Option.
Choice - Field will display one value out of a list of values, see Custom Field
Choice Option. Add or delete items in the choices by selecting “+” or “-”, in
the Choices section. Enter the option for the default value. To change from
the default option for a particular location, select another option from the
drop down list, see Custom Field Choice Option.
Figure 3.68: Custom Field List Option
Figure 3.69: Custom Field Choice Option
Formatting Rules
Formatting rules can be defined for PTP and PMP links and for the Access Point.
Formatting rules are used to control the color, style and visability of links and the
Access Point area in the project. They can also be used to exclude links and

Access Points (including its associated PMP Links) from reports and project exports
e.g. BOM and csv export files, at higher levels in the project:
A PTP Link will not be shown in the BOM or reports at the PTP Link Level.
An Access Point (and its associated PMP Links) will not be shown in the BOM
or reports at the hub or PMP network level. If all Access Points on a hub site
have been excluded, the hub site and any hub level equipment will not be
shown at the PMP network level.
A PMP Link will not be included in the BOM, reports or Performance Analysis
at the Access Point level, as well as the hub and PMP Network Level.
The rules can also be used to hide links and access points from the map views,
including the Google Earth (kmz/kml) files.
Each rule is tested against the links in the project. If the rule evaluates to “true”
for the link or Access Point, then the rule actions are applied. The rules are applied
in the order that they are defined in the Formatting List. To change the order of
the items, drag and drop them at the new location.
Figure 3.70: Link Formatting Page
Creating a Rule
To create a new rule click the appropriate node in the Navigation Tree. The PTP
Link Formatting node is used to define the rules for PTP links and the PMP
Formatting node is used to define the rules for PMP links and Access Points.
When the formatting panel appears click on the button. The Rule
Editor will appear.

Figure 3.71: Rule Editor
Basic Rule Settings
Option Description
Name The rule name
Description A description of the rule behavior (optional)
Stop executing If ticked, then any rules that come after this rule in the
when true? formatting rules list will not be tested against the link
Disable rule? If ticked then the rule is not tested against any links in the
project
Rule Groups and Expressions

The rule can consist of a number of Expression Groups. Each group can
contain one or more Rule Expressions. Within a group you can choose to test
that:
All of the expressions are successful (boolean AND)
Any of the expressions are successful (boolean OR)
You can also choose to test that All or Any of the expression groups are
successful.
Click on the + or - buttons to add and remove the Rule Expressions and
Expression Groups.

The individual expressions are used to test properties of the link. The Rule
Expression consists of the link property, a predicate and a value to test against.
Figure 3.72: Rule Expression
The property list contains many of the link and site attributes that can be viewed
in either the PTP Links panel (see Displaying PTP Links) or the PMP Links panel
(see Displaying PMP Networks), including custom fields created at the PTP Link,
Access Point or Subscriber Module levels. Where possible, the test value is
converted to a number before the rule is evaluated. All text-based comparisons
are case-sensitive.
When the rule expressions are modified, the rule is tested against the links in the
project. Any links that match the rule conditions are displayed in the
Links/Access Points affected by the rule list.
Several different actions can be set for links that match the rule.
Rule Actions
Option Description
Format link? Apply additional formatting to the link
Color The color of the link or access point. If the color is set to
white then the default color will be used.
Line thickness The thickness of the link line on the offline map. If left
blank then the default line thickness will be used.
Line style The line style used when displaying the link in the offline
map. If left blank then the default line style is used.
Exclude link/AP Links or Access Points (and associated PMP links) will not
from reports and appear in the reports or in any export formats (including
exports? the project level BOM and csv exports)
Hide link/AP on Links or Access Points will not appear in any of the maps
map views? (including Google Earth kml/kmz)
Hide PMP Links? Only available when Hide AP on map views is selected.
All PMP Links connected to the AP will not appear in any of
the maps (including Google Earth kml/kmz)
Copying Formatting Rules
One or more formatting rules can be copied from the Formatting list. Select one or
more rules that you wish to copy:
On Windows, hold the Ctrl key when selecting.

On OSX, hold the Command key when selecting (on some Apple keyboards,
this key also has an Apple logo).
Once you have selected the rules, right-click in the Formatting list and choose
Copy from the Formatting Rules Pop-up Menu.
Figure 3.73: Formatting Rules Pop-up Menu
Pasting Formatting Rules
If the clipboard contains any formatting rules then the paste commands will be
enabled. Click or Edit - Paste to paste the formatting rules into the current
project.
Equipment Templates
Equipment Templates can be defined for PTP links and PMP Equipment. The
default Equipment Template will be used to configure each new PTP link or access
point and subcriber module in the project. If the project does not contain an
appropriate equipment template then a default template will be generated when
required. This will then become the default equipment template.
A project can contain multiple equipment templates and, when combined with
Project Templates, they make it very easy to create many links or access points
and subscriber modules with a common starting configuration.
Existing links or access points can be configured with a template making it easy to
quickly change the configuration of one or more items (see Applying an
Equipment Template).

Figure 3.74: Equipment Templates Page
Creating a Template
To create a new equipment template click the appropriate node in the Navigation
Tree. The PTP Equipment Templates node is used to define the templates for
PTP links and the PMP Equipment Templates node is used to define the
templates for access points and subscriber modules. When the template panel
appears, click on the New Template button. The Equipment Template Editor will
appear. Note that the dialog will show a panel similar to the PTP link panel or a
composite of the access point and subscriber module panels as appropriate.

Figure 3.75: Equipment Template Editor
The equipment template can be configured in the same manner as a regular link
or access point. Note that for PTP links, only the Primary to Primary path or Link A
can be configured for 1+1 and 2+0 links. The other paths or Link B will be
configured with the same parameters as the Primary to Primary path or Link A.
Optional extras can be added to the template. Any item that uses the template
will then include the extras.
Setting the Default Equipment Template
The default equipment template will be used to configure any new links or access
points. There are three ways to set the default equipment template.
First, navigate to the Equipment Templates Page and select the appropriate

template in the equipment template list. Then follow one of the steps listed below:
Click
Edit the template and tick Set as default
Right-click on the template and choose Set as default from the Equipment
Templates Pop-up Menu
Creating a Template from an Existing PTP Link or Access Point
An equipment template can be created using the settings of an existing link or

access point. For PTP links, navigate to the PTP Links page and select the
appropriate link. For access points, select the access points from the Access
Points table under the PMP Links page or on a Hub page. Next, right-click and
click Save as equipment template from the pop-up menu.
Applying an Equipment Template
An existing equipment template can be applied to one or more links or access

points. To do this navigate to one of the table views such as the PTP Links page
or the Access Points table on the PMP Links page, then select the items that
require a new template. Right-click on one of the selections to display the Links
Pop-up Menu. Click Apply equipment template and then choose the
appropriate equipment template from the sub-menu.
Figure 3.76: Links Pop-up Menu
On an Access Point choose “Yes” to change all of the subscriber modules on the
Access Point to the default settings in the template, or choose “No” to only
change the Access Point parameters and keep the subscriber modules with their
individual settings.
Editing a Template
To edit a template, either:

Select the template in the list and then click Edit Template
Double-click a template in the equipment template list

Deleting Templates
One or more equipment templates can be removed from the project. Select one or
more templates:
Once you have selected the templates, either click the Delete button or
right-click in the Equipment Template list and choose Delete from the Equipment
Templates Pop-up Menu.
Figure 3.77: Equipment Templates Pop-up Menu
Copying Equipment Templates
One or more equipment templates can be copied from the Equipment Templates
list. Select one or more templates that you wish to copy:
Once you have selected the templates, right-click in the list and choose Copy
from the Equipment Templates Pop-up Menu.
Pasting Equipment Templates
If the clipboard contains any equipment templates then the paste commands will
be enabled. Click or Edit - Paste to paste the equipment templates into the
current project.
Channel Plans
Channel Plans only apply to PMP networks. Use the Channel Plans to define a
group of channels to be used within a PMP network. Allocate colours to each
channel to show a visualization of the frequency plan in the Offline Map. This is a
quick and easy way to spot potential issues.

To create an individual channel plan select New Channel Plan and a row will
be added to the Channel Plan. Set the Band, Product, Country, T/R Spacing,
Bandwidth and Raster from the drop down lists. Then choose the frequencies
for each channel from the drop down list in each channel. The list of available
frequencies for subsequent channels is dependent on the previous frequencies
selected.
T/R Spacing is only used by cnReach products. “Unpaired” uses the

same frequency for transmit and receive. When a T/R spacing is shown
the channels selected are the high channels used for the transmit
frequencies at the Access Point, the low frequencies are the AP transmit
frequencies minus the T/R spacing and are used as the transmit
frequencies at the SM.
If required increase or decrease the number of channels required.

To set the color for each Channel, either right click on the Channel and choose
Color or select the Channel and then click on Color from the toolbar.
To automatically create rows for the product configurations in the project file click
on Create Plans . A row for each Band, Product, Country and Bandwidth
combination will be added to the Channel Plan list.
To delete a Channel Plan click on Delete Channel Plan .
Figure 3.78: Channel Plan Menu
BOM Estimator
BOM Estimator can be used to quickly generate the Bill of Materials for a range of
PTP link types, PMP Access Networks or WiFi networks, without having to fully
define and configure individual PTP links or layout the access or WiFi network.
Retired products are not available in the estimates. IRFU, RFU_A and
long waveguide links, as well as the TDM Modules for PTP 810 links
cannot be estimated at this time.
Always use the latest version of LINKPlanner before generating a BOM
Estimate to ensure that the latest available parts are used. When
updating LINKPlanner check that all existing configurations are still as

required. If parts have been retired, removed or updated, existing

configurations will update automatically to the latest parts or change to
default parts, if the previous part has been removed or made obsolete.
Figure 3.79: BOM Estimator Panel - PTP
Creating a PTP Estimate
Select the PTP Estimates tab and click on the New Configuration button in the
PTP BOM Configuration panel to create an initial estimate and display the BOM
Estimate Dialog for PTP. The dialog shows a reduced set of options for configuring
a PTP link. Only options which can impact the BOM are available.
Link types that result in multiple paths, such as 1+1 Hot Standby, are all
configured through the single page. The secondary antenna selection
will appear in the end panel when required.

Figure 3.80: BOM Estimate Dialog for PTP
The estimate name defaults to a summary of the equipment configuration. The

name and description can be changed in either the estimate dialog or through the
PTP BOM Configuration table (Editing the Estimate Description). The item
quantity can be edited in the PTP BOM Configuration table (see Editing the
Quantity). To return to the default estimate name simply delete the current text.

Figure 3.81: Editing the Estimate Description
Figure 3.82: Editing the Quantity
The Bill of Materials for Link section in the PTP BOM Estimator Dialog shows
the equipment required for the single link. The PTP Network BOM Estimate
shows the equipment for each estimate multiplied by its link quantity to give an
overall BOM Estimate for the PTP network design.
Items which come in multi-packs are shown as the number of individual

items. To get the total number of packs required, divide the quantity by
the pack size.
Creating a PMP Estimate
Select the PMP Estimates tab and click on the New Configuration button in the
PMP BOM Configuration panel to create an initial estimate and display the BOM
Estimate Dialog for PMP. The dialog shows a reduced set of options for configuring
an Access Point in the top part of the panel. Only options which can impact the
BOM are available.

Figure 3.83: BOM Estimate Dialog for PMP
In the next section allocate all the Subscriber Modules required on this access
network. These are for all the access points of this type, not per access point.
Select the number of Integrated and Connectorized SMs required. For the
integrated SMs select the number and type of antenna enhancements from the
available list. For the connectorized SMs select the number of each type of
external antenna required.
The headings in bold show the total number of integrated and connectorized SMs
selected and the total number of subscriber modules allocated is shown in
brackets in the section header and in the SM Qty column of the PMP BOM
Configuration.
A warning will be shown if the number of external antennas is not the

same as the number of connectorized subscriber modules. If a custom
antenna is deleted from the Subscriber Module Antennas list it will
automatically disappear from the BOM Estimator.
The estimate name defaults to a summary of the Access Point equipment
configuration. The name and description can be changed in either the estimate

dialog or through the PMP BOM Configuration table in the same way as for PTP
Estimates. The number of Access Points can be edited in the AP Qty column of the
PMP BOM Configuration table, however the number of Subscriber Modules can
only be changed by editing the number of integrated and connectorized SM
options.
The Bill of Materials for Access Point section in the PMP BOM Estimator Dialog
shows the equipment required for the single access point and the Bill of
Materials for the Subscriber Modules shows the equipment required for all
the subscriber modules allocated for this access point network.
The PMP Network BOM Estimate shows the network equipment for each PMP
estimate multiplied by its AP quantity to give an overall PMP Network BOM
Estimate for the design. To add additional equipment at the hub sites, select New
Extra on the PMP BOM Network Estimate header and add the required parts
from the list of optional extras, then set the quantities for each part. Only the
quantities for the optional extras will be saved as changes with the project,
changes to quantities of the AP items at this level will not be stored. The PMP
Subscriber Modules BOM Estimate shows the total subscriber module
equipment for all PMP estimates to give an overall PMP Subscriber Module BOM
Estimate
Creating a WiFi Estimate
Select the WiFi Estimates tab and click on the New Configuration button in the
WiFi BOM Configuration panel to create an initial estimate and display the BOM
Estimate Dialog for WiFi. The dialog shows a set of options for configuring a WiFi
access point. Only options which can impact the BOM are available.
Figure 3.84: BOM Estimate Dialog for WiFi

The estimate name defaults to a summary of the WiFi equipment configuration.

The name and description can be changed in either the estimate dialog or through
the WiFi BOM Configuration table in the same way as for PTP Estimates. The
number of WiFi Access Points can be edited in the Qty column of the WiFi BOM
Configuration table.
The Bill of Materials section in the WiFi BOM Estimator Dialog shows the
equipment required for the single Access Point. To add additional items to the
BOM, click New Extra , this option is not available for all products. A
list of optional extras for the given product will be displayed. The list of items will
vary depending upon the product selected. To add an item to the BOM highlight
the option required and click OK. The item will appear in the main list, where the
quantity can be adjusted by selecting the number in the Qty column and
adjusting as required. To delete an optional item from the BOM list, highlight the
item and click Delete Extra .
The WiFi BOM Estimate shows the equipment for each estimate multiplied by its
quantity to give an overall BOM Estimate for the WiFi network design.
The WiFi equipment is not available for detailed network planning in

LINKPlanner, it is only available for BOM Estimates.
Exporting the BOM Estimate as a Spreadsheet
The BOM for all of the estimates for each of the BOM types (PTP, PMP Network,
PMP Subscriber Modules and WiFi) can be exported as a spreadsheet. To do this,
click , on any of the BOM Estimate panels. This
will open a spreadsheet containing the estimates for the project. The spreadsheet
will consist of the following, (see Estimate Spreadsheet):
an index sheet
a sheet containing the full BOM for all of the estimates; PTP, PMP and WiFi
a sheet containing the BOM for all PTP estimates
a sheet containing the BOM for all PMP Network estimates
a sheet containing the BOM for all PMP Subscribers
a sheet containing the BOM for all WiFi estimates
individual sheets for each PTP and PMP estimate configuration.

Figure 3.85: Estimate Spreadsheet
Best Server Analysis
The Best Server Analysis function only applies to PMP networks. Use the Best
Server Analysis function to automatically connect the subscriber sites in the
project to the access point that offers the best receive level for the specified
requirements. During the analysis the subscriber site is tested against each
access point that is in range. The analysis tests a range of products at the
subscriber, based on an ordered selection, along with all of the antenna
combinations that the product supports. Once the analysis is complete the PMP
links can be created.
The network layer of access points must be defined prior to running this
analysis.

Figure 3.86: Best Server Analysis Panel
The current access point equipment settings in the project are used to determine
which product families appear in the Best Server Analysis configuration panel.
Each product family has separate settings for:
Target SM Mode: Select the minimum modulation mode required at
the SM. This modulation mode is used to calculate the fade margin for
the link.
Target SM Fade Margin: Set the minimum fade margin that is
required at the Target SM Mode to consider the link valid.
Antenna Height: Set the required subscriber antenna height.
If the Target SM Mode is lower than the Min Mod Mode Required or
the Target SM Fade Margin is not large enough to support the Min
Availability Required, when the links are created they may not meet
the performance requirements for the PMP links.
In the SM Product Preferences list tick all SM products to be used in the
analysis, only subscriber products that can be supported by the current access
point configurations are displayed. Set the order in which the products are
prioritized. To reorder, select an item and then use the keyboard up and down
arrow keys or click the up and down arrow buttons. There must be at least one
subscriber product per product family otherwise the background turns pink and
the analysis cannot be started.

Figure 3.87: Best Server Analysis Configuration
When the subscriber product selection is valid, the button is enabled.

Tick the Omit connected places? checkbox to ignore any subscriber places that
are already connected to an access point. This is useful when adding new
subscriber sites to an existing project.
The analysis only considers the RF performance for an individual

subscriber module. The overall performance and loading of the access
point is the responsibility of the network planner.
Figure 3.88: Valid SM Product Selections
When the analysis starts, LINKPlanner first requests all of the required path
profiles before running the analysis calculations. The progress is displayed along
with the current run time (Analysis Progress). The process can be stopped at any
point, but the analysis will start from the beginning if it is later restarted.
Projects with a large number of access points and subscriber sites may

take a long time to process, particularly when there are a range of

products and antennas to test for each site.
Figure 3.89: Analysis Progress
The items in the project tree are disabled when the analysis is running to prevent
modifications to the project. Only the Best Server Analysis page is available.
Figure 3.90: Project Tree Disabled When Analysis Is Running
When the analysis is complete the results are displayed in the table. The top three
access points that achieve the design requirements are shown for each subscriber
site, not all subscriber sites will have multiple options. Any subscriber sites that
are unable to connect to any access point with the required performance appear
in red.
Click on the View in spreadsheet icon in the main toolbar to export the
results to a CSV file. To change which AP the subscriber connects to edit the
Selected AP for an individual subscriber or a group of subscribers.
Figure 3.91: Best Server Analysis Results

The Results Summary panel provides information on the connection status of

the subscriber sites.
Figure 3.92: Best Server Results Summary
Select the button to add all of the PMP Links to the project. If there are
existing subscriber modules in the project then the Update Subscriber Modules
dialog will appear.
Yes: Select to remove the existing subscriber modules and replace with
the new best server options.
No: Select to update existing subscriber modules to the current
configuration from the best server results. This may change the
product, antenna and antenna height settings for matching subscriber
modules. Where the new analysis connects a site to a different AP a new
subscriber module will be created to that AP without deleting the
existing subscriber module. This may result in multiple links from each
subscriber site.
Cancel: Select to abandon the command without modifying the project.
Figure 3.93: Update Subscriber Modules

If the project is closed without creating the subscriber modules then a warning will
appear (see Closing a Project without Creating Subscriber Modules).
Best Server Analysis results are not stored in the LINKPlanner project
file. If the project is closed without applying the results then the analysis
results will be lost.
Figure 3.94: Closing a Project without Creating Subscriber Modules
Purge Unused Profiles
The LINKPlanner project file may contain additional profiles for links that no longer
exist in the project file. This can happen when a link has been deleted or as a
result of running the Best Server Analysis. A large number of profiles can
dramatically increase the size of the project file on disk. To reduce the size of the
files select Project, Purge unused profiles.
Figure 3.95: Purge Unused Profiles Command
The Purge unused profiles command displays a confirmation dialog before

modifying the project file. Click Yes to remove the profiles, the status bar will
display the number of profiles that have been removed.

Figure 3.96: Purge Unused Profiles Confirmation
Figure 3.97: Status Showing the Number of Profiles Removed

Exporting and Reporting
Site and Link data can be exported in CSV or KML format, as described in
Exporting Data.
Reports can be created in PDF format for the currently open and selected project,
as described in Creating Reports.
Exporting Data
Data can be exported in CSV or KML format for the currently open and selected
project.
PTP Links (CSV)
To view the PTP link details in Excel, click the “PTP Links” node in the navigation
tree and click View in Spreadsheet .
To export the link details to a CSV file, click File, Export, PTP Links (csv). The
CSV file can then be incorporated into a spreadsheet to enable further analysis
and costing of the project.
Network Sites (CSV)
To export details of all Network sites to a CSV file, click File, Export, Network
Sites (csv).
Subscriber Sites (CSV)
To export details of all Subscriber sites to a CSV file, click File, Export,
Subscriber Sites (csv).
PTP Links from this site (CSV)
To export details of all PTP links from a single site to a CSV file, click File, Export,
PTP Links from this site (csv).
Hubs (CSV)
To view the Hubs in Excel, click the “PMP Links” node in the navigation tree and
click View in Spreadsheet under Hubs.
To export details of all Hubs to a CSV file, click File, Export, Hubs (csv). The CSV
file can then be incorporated into a spreadsheet to enable further analysis and
costing of the project.
Access Points (CSV)
To view the Access Points in Excel, click the “PMP Links” node in the navigation
tree and click View in Spreadsheet under Access Points.

To export details of all Access Points to a CSV file, click File, Export, Access
Points (csv). The CSV file can then be incorporated into a spreadsheet to enable
further analysis and costing of the project.
Subscriber Modules (CSV)
To view the Subscriber Modules in Excel, click the “PMP Links” node in the
navigation tree and click View in Spreadsheet under Subscriber Modules.
To export details of all Subscriber Modules to a CSV file, click File, Export,
Subscriber Modules (csv). The CSV file can then be incorporated into a
spreadsheet to enable further analysis and costing of the project.
Google Earth(TM) (KML)
To export details of a single site to a KMZ/KML file, click File, Export, Google
Earth (kmz/kml). The KMZ/KML file can then be used to view the project sites in
Google Earth(TM).
Performance Chart Data (csv)
To export the data behind the PTP performance charts to a csv file, click File,
Export, Performance Chart Data (csv). This generates a four column table of
Link Name, Site Name, Availability and Throughput, which can then be post
processed as required.
FCC License Coordination
To export the information required for submission to the FCC Licensing

Coordination body, click File, Export, FCC License Coordination. The
information will be exported to a CSV file, in the format required by Comsearch.
This is only available for licensed band PTP links.
PTP 450 / PMP 450 Configuration Files
To export the configuration files for PTP 450 and PMP 450 sites, click File, Export,
PTP450/PMP450 Configuration Files. The information for all PTP 450 and PMP
450 sites will be exported to the selected folder and stored in separate sub-folders
for PTP and PMP links. All PTP/PMP 450 ends must have a MAC Address before
being exported, (see Configuration at Each End (one end shown) for PTP links,
Access Point Details for Access Points and Subscriber Module Description for
Subscriber Modules).
The configuration files exported from LINKPlanner only contain information
defined within LINKPlanner, including location details and equipment
configuration, such as country, bandwidth, transmit power, antenna gain,
downlink data, control slots etc.
Exporting and Reporting 139

Site names which contain non-ASCII characters will not be included in

the configuration file, as they cannot be displayed in the product.
PTP 450 / PMP 450 FCC Device Registration
To export the information required to register the Radio Locations for 3.65 GHz
devices on the FCC website, click File, Export, PTP450/PMP 450 FCC Device
Registration. The information will be exported to a CSV file in the order required
by the online process for each AP and SM in the project.
There are a number of columns where the information is not directly available
from the usual project fields. To include the information for these columns into the
CSV file use the Custom Fields functionality to create fields for each column
heading, see Custom Fields. For the Access Points it is recommended to configure
the fields at the Hub as the information will usually be the same for a given
location, any information entered for an individual AP will overwrite the Hub data
for the same field. For Subscribers configure the fields at the Subscriber Module
level. The Custom Fields must use exactly the same names as in the column
headers in the csv, as shown below:
FCC ASR Number
City
County/Borough/Parish
State
Support Structure Type
To automatically create these fields at the PTP End, Hub, Access Point and
Subscriber Module level, click Project, Create FCC Device Registration Fields.
Creating Reports
Reports can be created in PDF format for the currently open and selected project.
There are four categories of report:
PTP Proposal reports offer a general overview. Options are Project or PTP
Link.
PTP Installation reports contain detailed configuration and performance
parameters. Options are Project or PTP Link.
PMP Proposal reports offer a general overview. Options are Project, Hub or
Access Point.
PMP Installation reports contain detailed configuration and performance
parameters for the PMP Links to Subscriber Modules. Options are Project,
Hub, Access Point or PMP Link.
Installation reports contain ordered lists of field settings. These are very
useful when completing the Installation Wizard of the ODU web
interface.

PTP Proposal Reports
To obtain a PTP Proposal report, open the required page from the navigation tree
(PTP Links list, or PTP Link), then choose to preview or create the report:
To preview, click Proposal Report PDF

To create as a PDF, click File, PTP Proposal Reports and one of Project or
PTP Link.
The Project proposal report consists of a project summary (customer details,
network map, list of links and BOM) and plans of each link (path profile,
throughput, link summary, performance charts, climatic factors & losses and
BOM).
The PTP Link proposal report consists of a project summary, path profile,
throughput, link summary, performance charts, climatic factors & losses and BOM.
PTP Installation Reports
To obtain a PTP Installation report, open the required page from the navigation
tree (PTP Links list or PTP Link), then choose to preview or create the report:
To preview, click Installation Report PDF

To create as a PDF, click File, PTP Installation Reports and one of Project
or PTP Link.
The Project installation report consists of a project summary (customer details,
network map, list of PTP links and BOM) and details of each PTP link (link
summary, path profile, link configuration, site installation notes, detailed
throughput data and regulatory conditions).
The PTP Link installation report consists of details of one PTP link (link summary,
path profile, link configuration, site installation notes, detailed throughput data,
regulatory conditions and BOM).
PMP Proposal Reports
To obtain a PMP Proposal report, open the required page from the navigation tree
(PMP Links list, Hub, or Access Point), then choose to preview or create the report:
To preview, click Proposal Report PDF

To create as a PDF, click File, PMP Proposal Reports and one of Project,
Hub or Access Point.
To limit the Project and Hub level reports to only show the Network level
information tick the Network layer only in PMP Installation Report option
under Tools, Options (Preferences in Mac), Reports. This significantly reduces
the size of the report where there are a large number of subscribers.
The Project proposal report consists of a project summary (customer details,
network map, list of Access Points, a BOM for PMP Network Equipment and a BOM
for Subscriber Equipment). This is followed by a Hub report for each Hub in the
project, which in turn includes the details for each Access Point.
Exporting and Reporting 141

The Hub proposal report consists of a project summary, a Hub Summary including
a network map for the Hub, list of Access Points, and a BOM for the Network
Equipment. This is followed by an Access Point report for each Access Point on the
Hub.
The Access Point proposal report consists of a project summary, an Access Point
Summary, a Subscriber Module Summary, detailed throughput data for the Access
Point, a BOM for the Access Point Equipment and a BOM for the Subscriber Module
Equipment.
PMP Installation Reports
To obtain a PMP Installation report, open the required page from the navigation
tree (PMP Links list, Hub, Access Point or Subscriber Module), then choose to
preview or create the report:
To preview, click Installation Report PDF

To create as a PDF, click File, PMP Installation Reports and one of
Project, Hub, Access Point or PMP Link.
To limit the Project and Hub level reports to only show the Network level
information tick the Network layer only in PMP Installation Report option
under Tools, Options (Preferences in Mac), Reports. This significantly reduces
the size of the report where there are a large number of subscribers.
The Project installation report consists of a project summary (customer details,
network map, list of Access Points and BOM). This is followed by a Hub report for
each Hub in the project, which in turn includes the Access Point and details of
each PMP link, see the sections below for details on each lower level report.
The Hub installation report consists of a project summary (customer details,
network map of the hub area, list of Access Points and BOM). This is followed by an
Access Point report for each Access Point on the Hub and details of each PMP link.
The Access Point installation report consists of a project summary, Access Point
Summary, installation notes for the Access Point, network map of the Access Point
area, detailed throughput data for the Access Point, BOM and details of each PMP
link.
The PMP Link installation report consists of details of one PMP link (link
summary, path profile, installation notes for the Subscriber Module, Performance
reports and BOM).

CHAPTER 4
Planning PTP links
The goal of PTP link planning is to ensure that each direction of the link will
perform to an acceptable level, measured by the Throughput and Availability
values in the Performance Summary section of the Link Page. To allow
LINKPlanner to predict Throughput and Availability, the planner must enter the
variables that affect link performance, such as: band, region, equipment, antenna,
height, terrain, obstructions and reflection.
To achieve this goal, follow this process:
1. Start the application and set options. See Starting the Application.
2. Build a project to model a PTP link (or network). See Projects.
3. Enter details of all sites in the project. See Sites.
4. Define the links between sites, create profiles of those links and update the
profiles with details of obstructions. See Links.
5. Adjust the link profile to allow for terrain height variance, obstructions and
reflection. See Adjusting Link Profiles.
6. Confirm that the link will perform to an acceptable level, measured by the
Throughput and Availability values in the Performance Summary section of
the Link Page.
7. Export and report project, site and link data. See Exporting and Reporting
8. If TDD Synchronization is required, see Setting TDD Synchronization
9. If Hot Standby Protection is required, see Setting Hot Standby Protection
(1+1)
10. If 2+0 Antenna Sharing is required, see Setting 2+0 Antenna Sharing
11. If ODUs are to be mounted indoors or at the base of the tower, see Long
Waveguide
12. If Spatial or Frequency Diversity is required, see Setting Diversity
143
Links
Define the links between sites, obtain profiles of those links and enter link details.
The process for each link is:
1. Create a new link by either importing from a spreadsheet as described in
Importing PTP Links from a Spreadsheet or by connecting existing sites as
described in Creating PTP Links.
2. Display the list of links in the project and open the new link, as described in
Displaying PTP Links.
4. Enter the variables that affect performance, such as band, region,
equipment, antenna and height. See Link Page.
For more information on improving the performance of links, see Optimizing E1 or
T1 Latency, Setting TDD Synchronization, Setting Hot Standby Protection (1+1),
Setting 2+0 Antenna Sharing and Long Waveguide.
Importing PTP Links from a Spreadsheet
Use this method when PTP link information is in a spreadsheet. The required fields
for each link are Name, Local Latitude, Local Longitude, Remote Latitude and
Remote Longitude. The optional fields are Description, Local Antenna Height and
Remote Antenna Height (Link Data in a Spreadsheet).
The PTP link import file only imports the coordinates and heights, which
is different from the format in which PTP links are exported from
LINKPlanner as the export contains all the detailed link parameters. An
exported PTP link CSV file cannot be imported directly back into
LINKPlanner, without being edited to reduce it to the required columns.
The procedure is:
Figure 4.1: Link Data in a Spreadsheet
144 Chapter 4. Planning PTP links

1. Import the data from a CSV file.

To import from CSV: save the spreadsheet as a CSV (comma separated) file;
then in LINKPlanner, click File, Import, PTP Links from CSV.
2. The Table Import Wizard is presented:
LINKPlanner attempts to detect the correct delimiter and encoding for each
CSV file, but it does not always succeed. If the data is not displayed in the
correct columns, specify a different delimiter or encoding.
Figure 4.2: Table Import Wizard
3. Select the columns to be imported:

If the first row contains column headings, tick Skip first row.
For each column, select the correct attribute for the data in the column.
Ensure that unwanted columns are ignored (Selecting Columns to be
Imported). The antenna height values may be specified in feet or meters.
Select multiple Description columns if required, but select the other columns
once only.
Links 145
Figure 4.3: Selecting Columns to be Imported
4. Correct any values that cannot be imported:

If LINKPlanner cannot interpret any of the values (for example, if a latitude or
longitude is not formatted correctly), the cell is highlighted in red.
Double-click in a red cell to edit it (Link Value Cannot be Interpreted).
Figure 4.4: Link Value Cannot be Interpreted
If site coordinates match (1m tolerance) site locations in the current

project file then the matching cells will highlight in yellow and a warning
will appear. It is still possible to import the data, but it will result in
duplicate sites or links in the project file.
5. Verify the map of newly imported links:
The wizard displays a map of the new links and sites to confirm that the
positions are correct (Map of Newly Imported Sites and Links). If they are
correct, press Finish.

Figure 4.5: Map of Newly Imported Sites and Links
Pasting Links from Spreadsheet Data
Use this method when link information is in a spreadsheet. The required fields for
each link are Name, Description, Left Latitude and Longitude and Right Latitude
and Longitude. The data does not need to contain any column headings and any
invalid data is ignored.
The procedure is:
1. Import the data either by copying from either a tab-delimited file or from a
spreadsheet.
To import from a spreadsheet, select the data and click Edit, Copy; then
in LINKPlanner, click Edit, Paste PTP Links.
Figure 4.6: Importing Links From a Spreadsheet
Links 147
Any invalid data will be ignored

The end names will be created by splitting the link name on the word “to” if
possible
The coordinates are assumed to be a decimal number with negative values
for South and West
If any of the sites being pasted are within 1 meter of an existing site then the
existing site will be used instead
Creating PTP Links
To create a new PTP Link, either click Project, New PTP Link (Ctrl-L), or click
New PTP Link . The New PTP Link page is displayed.
This is an example of a completed New PTP Link Page:
Figure 4.7: New PTP 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 network site from
each list and hit OK. The PTP link is made between those two locations and the
PTP Link page is displayed.

Multiple PTP links can be selected from the To list if required.

Displaying PTP Links
When one or more links have been created, they appear in the PTP Links list and
can be opened in the Link Page. To display this list, click the “PTP Links” node in
the navigation tree.
Figure 4.8: PTP Links List
By default, if the link is displayed in red, it means that the predicted performance
of the link is below requirements. It is possible to alter the default colors in the
Graphics Page. Additional formatting settings can be applied using Formatting
Rules.
Customizing the PTP Links list
The PTP Links list display can be customized, to manage the information displayed
in the list, see Managing List Views.
Copying Links
To select one or more links for copying:

When links have been selected, right-click in the PTP Links list and choose Copy
from the PTP Links Pop-up Menu.
Links 149
Figure 4.9: PTP Links Pop-up Menu
Duplicating Links
To duplicate links, select one or more links and choose Duplicate from the PTP
Links Pop-up Menu. The new versions will have the same attributes as the original
links.
Deleting Links
The Links list can be used to delete links altogether. To delete a link, right-click
over it and click Delete Links from the PTP Links Pop-up Menu.
Editing Link details
A number of link attributes can be edited in the Links list. To edit the link attribute,
select the link in the list and right-click on the cell that you wish to change. The
PTP Links Pop-up Menu will appear. Choose Edit <attribute-name> (where the
attribute name will be the name of the column heading). The same attribute can
be edited for several links at the same time. If the new value is not valid for the
other link settings (e.g. choosing a PTP250 product even though the band is set to
38 GHz) will result in a warning and the product value will not update.

Figure 4.10: Editing a Property for Multiple Links
To edit any other Link attribute, open the link using one of the following methods:
Single-click the link node in the Navigation tree.
Double-click on the link in the Links list.
The Link Page is displayed.
Viewing & saving the list in MS Excel
To view the list in Excel, click View in Spreadsheet while viewing the list.
Once in the spreadsheet the file can be saved as normal. To export only the
columns shown in the list select Tools, Options (Preferences in Mac), Reports
and select the option Only export visible columns to CSV file, see Options
(Preferences).
Links 151
Link Page
Use the Link page 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 are displayed 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. Use this feature to evaluate the
impact of step changes on link performance.
If a field is highlighted in pink, its value is out of the permitted range.
The Link page contains the following sections:
Link Description and Equipment
Profile
Configuration at Each End
Performance Summary
Performance Details
Bill of Materials for Link
Link Description and Equipment
Link Description
Enter the Name and Description of this link. The default contact information for
Cambium Networks will be shown. When the link profile has been received the
information will change to show the Sales Contact information for the location of
the link. To update this information click Refresh.
Figure 4.11: Link Description

Equipment (unlicensed bands)
Select the equipment, regulation and optimization method for this link. The fields
that are displayed in the “Equipment” box will change depending on the type of
equipment selected. For example, when a PTP 600 is selected, the E1/T1 field is
displayed.
Figure 4.12: Equipment (unlicensed bands)
Region and equipment

Band: Select the frequency band used by the link.
Product: Select the PTP bridge product. For PTP 650S select PTP 650
Product, Full Capacity key and Small Form Factor Antenna. For PTP 650L
plan the performance as for PTP 650S limiting the bandwidth to 5 or 10
MHz, or up to 30 MHz with the upgrade key.
Remote Product: (PTP 700 only) Select a different PTP bridge product
for the remote end of the link. The link will default to the same product
at both ends of the link.
Color: (PTP 700 only) Select the color of the radios.
Capacity: (PTP 650, 670 and 700 only) Select the capacity variant
required.
Regulation: Select the regulation that applies to the region in which
the link is located.
Encryption Variant: (PTP 250, PTP 450 and PTP 450i only.) Select the
encryption option for the link, used for product selection only.
Precise Network Timing: (PTP 650, 670 and 700 only) Select Enable
to add license key for IEEE1588 and Synchronous Ethernet to BOM.
Precise Network Timing is added by default for PTP 650S. Select Disable
to carry telecoms traffic.
ePMP PTP Mode: (ePMP only) Select the operating mode required.
Select ePTP, where available, for low latency and/or Adaptive
Symmetry.
Link Type: (PTP 550 and N500 Only) Select the Link Type required.
I/O Connectivity: (N500 Only) Select Expanded to get the additional IO
port, used for product selection only.
Sync Input: (N500 Only) Select the synchronization option for the link.
Dynamic Payload: (N500 Only) (information only)
Link Page 153

Configuration
Bandwidth: Select the channel bandwidth.
Band Setting: (N500 Only). Select ISM or Licensed.
E1/T1: (PTP 300, 500, 600, 650, 670 or 700). If the link is to carry
telecoms traffic, select the number of E1 or T1 links required. For more
information, see Optimizing E1 or T1 Latency.
Optimization: (PTP 300, 400, 500, 600, 650, 670 or 700). Select the
optimization for the link, either for IP Traffic or TDM Traffic. If TDM is
enabled, the link is optimized automatically for TDM traffic/latency.
Sync: (PTP 300, 500, 600, 650, 670 or 700). Defaults to Disabled. If
TDD Synchronization is required, select the required Sync option. For
more information, see Setting TDD Synchronization and TDD
Symmetry: (PTP 300, 400, 500, 600, 650, 670 or 700). Select the link
operation (Adaptive, Symmetric, 2:1, 3:1 or 5:1 - options are dependent
on Product and other configuration settings).
Dual Payload: (PTP 300, 400, 500, 600, 650, 670 or 700). Allow
dual-payload modulation modes for better throughput.
Modulation Type (N500 ISM Only) Select the group of modulation
modes to use.
Modulation Mode: (N500, PTP 250). Select the modulation mode to be
used by the equipment.
Highest Mod Mode: (PTP 650, 670 and 700 only). Select the highest
modulation mode for the Ethernet traffic to limit the maximum
throughput rate, default is 256 QAM 0.81 (no limit). Dual or Single will
be automatically selected depending on the setting for Dual Payload.
Maximum Mod Mode: (ePMP, PTP Mode, or N500 only). Select the
highest modulation mode for the Ethernet traffic to limit the maximum
throughput rate, default for ePMP is MCS15.
Minimum Mod Mode: (N500 only) Select the lowest modulation mode
for the traffic. Note that the lowest Minimum Mod Mode will not be more
than four modes below the Maximum Mod Mode.
Lowest Ethernet Mode (PTP 600, 650, 670 and 700 only). Select the
lowest modulation mode for the Ethernet traffic to achieve the required
throughput rate, default is BPSK 0.63 Single.
Lowest Telecoms Mode (PTP 300, 500, 600, 650, 670 or 700). When a
link is configured for E1 or T1 telecoms traffic, select the lowest
modulation mode to achieve the required latency. For more information,
see Optimizing E1 or T1 Latency.
Color Code: (PTP 450 and 450i only). Select the Color Code for the link
(information only).
Frame Period: (PTP 450 and 450i only). Select the Frame Period.

Downlink Data: (PTP 450 and 450i only). Set the proportion of the link
to be used for throughput from the Master to the Slave.
DL/UL Ratio: (ePMP only). Select the required DL/UL Ratio, where DL is
the proportion of the link to be used for throughput from the Master to
the Slave.
Hop Pattern: (N500 only). Select the uniform step interval for DTS
modulations. A value of 0 sets the frequency to a single channel, a
value of 1 creates a pseudo random hopping sequence. A value of 1
must be used when Modulation Type = FHSS.
MMS Hop Offset: (N500 only). Select the MMS Hop Offset for the link,
only available when Sync Input is enabled.
Polarization: (N500 only). Select the antenna polarization to be used
(Horizontal or Vertical).
Master: Select which site is the master.
Gb Ethernet Port: (ePMP only). Select whether each end of the link
requires equipment with a GbE port instead of an FE port (the FE port
will limit the maximum throughput if selected at either end of the link).
Select Gb Ethernet Port at the Master if the link has to be synchronized.
When TDD synchronization is enabled for a link, the link will

show zero data rate until a valid set of global options are
selected in the TDD Synchronization List
Frequency Configuration (N500 only)
Band Start: Select the lower band edge frequency, default for 900 MHz
ISM is 902 MHz.
Band Stop: Select the higher band edge frequency, default for 900
MHz ISM is 928 MHz.
Exclude Lower: Select the lower frequency to be excluded, a value of 0
MHz indicates no lower limit. This value must be between the Band
Start and Band Stop frequencies.
Exclude Upper: Select the upper frequency to be excluded, a value of
0 MHz indicates no upper limit. This value must be between the Exclude
Lower and Band Stop frequencies.
Equipment (licensed bands)
Select the equipment, regulation and configuration for this link.
Link Page 155

Figure 4.13: Equipment (licensed bands)
Region and equipment

Band: Select the frequency band used by the link.
Product: Select the PTP bridge product using either ODU-A, ODU-B or
IRFU where available for PTP 800 and PTP 810. For further information
on the two ODU types see PTP 800 Series User Guide or PTP 810 Series
User Guide.
Regulation: Select the regulation that applies to the region in which
the link is located.
Long Waveguide: (PTP 800 with ODU-A Only) Select which end of the
link requires a long waveguide, see Long Waveguide.
Link Type
Defaults to 1+0 for a basic single link configuration.
If using Hot Standby or Spatial Diversity equipment click 1+1
Hot Standby (for PTP 820C Spatial Diversity click on 2+0
Spatial Diversity), for more information, see Setting Hot
Standby Protection (1+1) and Setting Diversity.
If using Frequency Diversity click 1+1 Frequency Diversity
(PTP 810 Only - not available with FCC regulations), see Setting
Diversity.
If using 2+0 Antenna Sharing click either 2+0 Co-Polar
(ACCP), 2+0 Cross Polar (ACAP) or 2+0 XPIC (CCDP) (only
the Co-Polar variant is available for the IRFU with PTP 800 and
XPIC is only available for PTP 810, PTP 820C and PTP 820G and
on LOS links), for more information, see Setting 2+0 Antenna
Sharing.
If using Hot Standby and 2+0 click either 2+2 Co-Polar
(ACCP), 2+2 Cross-Polar (ACAP) or 2+2 XPIC (CCDP) (only
available on PTP 820C and XPIC is only available on LOS links)
If using 4+0 Antenna Sharing click either 4+0 Co-Polar
(ACCP), 4+0 Cross-Polar (ACAP) or 4+0 XPIC (CCDP) (only
available on PTP 820C and XPIC is only available on LOS links)
Capacity Key: (PTP 810 Only) Select the capacity key for the link.
When this is changed the list of available bandwidths and modulation
modes may also change. For 2+0 links select the capacity required for
the aggregate link, this will automatically be divided equally between
the two individual links.

Path Aggregation: (PTP820 Only) Select Aggregate Paths to share

the radio configuration between all paths and show aggregated
throughput and performance at the parent level. Select Independent
Paths to set parameters such as T/R spacing, bandwidth and
modulation mode differently on each path, use this mode if using
different traffic paths on each radio. The performance is shown
independently for each path and there is no aggregated performance at
the parent level. (The independent path option is not available for XPIC
and PTP820C Spatial Diversity link types)
Remote Mount: (PTP 820 Only) Select which end of the link requires
the antenna to be remote mounted.
Ethernet Configuration: (PTP 820C Only) Select the required Ethernet
Configuration for 2+0 Link Types. Single Ethernet (MC-ABC) restricts the
capacity to < 1 Gbps based on the capability of a single Ethernet
connection. To access the full capacity of the radio link, select one of the
Multiple Ethernet Options, which require additional Ethernet connections
to the radio.
I/O Connectivity: (N500 Only) Select Expanded to get the additional IO
port, used for product selection only.
Sync Input: (N500 Only) Select the synchronization option for the link.
Dynamic Payload: (N500 Only) (information only)
Configuration
Band Setting: (N500 Only) Select ISM or Licensed.
T/R Spacing: Select the difference between transmit and receive
frequencies (MHz).
Bandwidth: Select the channel bandwidth.
Modulation Mode: Select the modulation mode to be used by the
equipment. If Adaptive is selected then additional fields are displayed
(not available for PTP 810).
Maximum Mod Mode: Select the maximum modulation mode that the
equipment will use in adaptive mode. Only displayed when Adaptive
modulation is selected.
Minimum Mod Mode: Select the minimum modulation mode that the
equipment will use in adaptive mode. Only displayed when Adaptive
modulation is selected.
Polarization: Select the antenna polarization to be used (Horizontal or
Vertical).
ATPC: Select whether the link will be configured with ATPC enabled or
disabled. In some bands and regulations it is compulsory to use ATPC, in
which case it will not be possible to disable the function. For PTP 800 it
is recommended to Enable ATPC for shorter links to optimize the power
control function. For PTP 810 this option is called APC and it is
recommended to leave it disabled.
Master: (N500 only) Select which site is the master.
Link Page 157

Hi: Select which site is the nominated Hi end for the link. This site will
only have access to the higher end of the frequency range and the other
end of the link will only have access to the lower frequencies in the
band.
Header Compression: (PTP 820 Only) Select the level of header
compression required.
Figure 4.14: TDM Equipment Configuration (PTP 810 Only)
TDM Configuration (PTP 810 Only)

Select the STM-1, E1/T1 and associated modules for this link, see TDM Equipment
Configuration (PTP 810 Only).
STM-1: Select the number of STM-1 to be passed across the wireless
link. Limited to a maximum of 2 for 1+0 or 1+1 Link types or 3 for 2+0
Link Types.
STM-1 Modules: Only displayed if STM-1 is greater than zero. Select
the extra module(s) required to terminate the STM-1 on the front panel
of the MMU. In a 1+0 this may be None, if the STM-1 is being passed
between the East and West modem in a Dual 1+0 configuration.
E1s (or T1s): Select the number of E1 or T1 circuits to be carried
across the wireless link. These may arrive at the front panel of the MMU
as an STM-1 before being multiplexed / demultiplexed onto the wireless
link. If the regulation is ETSI, E1 will be displayed, if the regulation is set
to FCC or Canada, T1 will be displayed. Some values of E1 (or T1) are
not supported for a given modulation and bandwidth due to timing
restrictions and are not shown in the selection list for the given
modulation and bandwidth.
TDM Modules: Only displayed if E1 or T1 is greater than zero. Select
the extra module(s) required to terminate the E1 or T1 circuits on the
front panel of the MMU. This may be None if there are sufficient ports
on the MMU Master I/O card or if the E1 or T1 are being passed between
the East and West modems in a Dual 1+0 configuration.
Remaining Ethernet: Displays the amount of Ethernet traffic which is
potentially available in addition to the TDM requirements, using either
one of the Fast Ethernet MMU Models or one of the GigE MMU Model
configurations. Which MMU Models are actually available is dependent
upon the configuration of STM-1, E1 or T1 and the extra modules
selected, see Configuration at Each End to set the MMU Model.
2 x STM-1 Interface: Only displayed if one of the 2 x STM-1 modules
has been selected for either STM-1 or E1/T1. Select either an optical or
electrical interface.

Mini I/O Interface: Only displayed if the Mini I/O module has been
selected for either STM-1 or E1/T1. Select either an optical or electrical
interface.
TDM Configuration (PTP 820G Only)
Select the E1/T1 required for this link
TDM Type: Defaults to None, if TDM is required select either
E1 or T1.
E1s (or T1s): Select the number of E1 or T1 circuits to be
carried across the wireless link. In 2+0 configurations the
maximum of 16 is shared between the two paths.
Profile
This section contains a visualization of the path between the two sites (Profile with
Trees).
In this example, a 12m high tree at 22.904 km and and an 8.0 m high tree at
24.912 km enter the Fresnel zone and alter the slope.
Figure 4.15: Profile with Trees
Color code used in the profile:

Brown: terrain.
Green: obstructions (such as trees or buildings).
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.1% of the time. Sometimes
known as Worst Earth curvature (Ke).
To update the profile to allow for terrain height, obstructions and water reflections,
see Adjusting Link Profiles.
Link Page 159

The Fresnel zone shown is a visualization of F0.6 or 0.78F1 , which is shown for
guidance when setting antenna heights for path clearance. It is not used directly
in the diffraction loss calculations.
When planning high availability links (better than 99.9%) the antenna heights
should be set to ensure that the grey line does not penetrate into the Fresnel zone
shown.
To view the profile in Google Earth(TM), click the Google Earth toolbar icon .
For more information, see Using Google Earth(TM).
Path to display: (PTP 820C 2+0 SD Only) Choose the path to display from the
following options:
Main: the main path using the antenna heights defined for the main antenna
at each end
Main to Diverse: the path between the local main antenna height and the
remote diverse antenna height
Diverse to Main: the path between the local diverse antenna height and
the remote main antenna height
An additional shortcut menu is available by right-clicking on the profile which will
give access to the following items:
Copy: selecting this option copies the profile information. It can then be pasted
into another link or into an Excel spreadsheet or text editor, see Updating Link
Profiles.
Paste: this option is only available if a profile has previously been copied either
from another profile or from a spreadsheet, see Updating Link Profiles.
Edit Profile: selecting this option displays the Profile Editor, see Updating Link
Profiles.
Edit Reflection Parameters: selecting this option displays the Reflection Editor,
see Updating Link Profiles.
Reverse Link: Selecting this option will reverse the ends on the link, for example
a link “End A to End B” will become “End B to End A”, with associated changes to
the Link Description and report titles. All properties associated with an end will
move with the end, for example antenna and power configurations and
Master/Slave or Hi/Lo settings.
Configuration at Each End
Use this section to evaluate different antenna configurations at each end of the
link. Enter data about the antenna, transmission power and interference density
(at both ends). In response, the Performance Summary section is updated
automatically to show the effect upon the Mean Throughput, Minimum
Throughput and Availability. The two 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.
Figure 4.16: Configuration at Each End (one end shown)
Antenna: Select the required antenna from the drop-down list. The list can be
sorted by any column by clicking the column heading. If operating in the
unlicensed band and the required antenna is not in the list, click Other... and
enter the details in the User Defined Antenna page. Antennas may also be
viewed, created, edited and deleted from the Available Antennas page. Licensed
band antennas may only be viewed, at present only Cambium supplied antennas
are supported at these frequencies.
Antenna Height (meters): This is the height of the antenna 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): In licensed band displays the diversity spacing as
a read only parameter, to change the diversity spacing adjust the height of the
secondary or diverse antenna. When in the unlicensed band this field is only
displayed if a single polar external antenna is selected, set the diversity spacing
height required. Tick the reflection mitigation to use the diversity to combat
reflections, leave unticked for protecion against tropospheric multipath. See
Setting Diversity, for more information on how diversity operates for the different
products and configurations.
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 or waveguide that connects the radio to the
antenna (EWP52, EWP63, LFD4.5-50, 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
Link Page 161

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.
Max Payload Bytes: (N500 only) Set the maximum packet size. Maximum value
is 1600 Bytes. Minimum value for fixed modulation mode is 64 Bytes, in adaptive
mode, the minimum may be higher than this dependent on the configured Max
and Min Modulation modes. Reducing the packet size will reduce the data rate
from the quoted data rate per mode.
Tx Frequency: (PTP 550 Only) To change transmit frequencies for the link, click
on Select.... The Select Transmit Frequencies dialog is displayed. For PTP 550
this dialog only shows one frequency selection per path, as the same frequency is
used for transmit and receive.
Interference (dBm): This is the amount of site noise in the selected 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. The
bandwidth displayed depends on the bandwidth selected in the Equipment
Settings box (in this example it is 15 MHz). To enter Interference, tick the box and
update the default value. If the link has been set up and mean power
measurements from DFS are available, then use these measurements.
MAC Address: This is an optional field where the MAC Address can be recorded.
It is required when exporting PTP 450 configuration files.
Licensed bands
For links operating in licensed bands, the following additional attributes are
displayed:
Antenna Configuration: (1+1 HSB and 2+2 configurations only) Select the
required coupler or antenna configuration.
Feeder Loss: This replaces the Cable Loss field in the unlicensed band. The
licensed band equipment uses a flexible waveguide, which is of a fixed length and
the feeder loss is automatically entered when a non-integrated antenna is used.
This field is also used to display other fixed losses, for example the coupler loss in
the Protected Hot Standby mode. When using a common non-integrated antenna
in Hot Standby this field will show the sum of the feeder loss and coupler loss.
To change the automatic feeder loss click Edit and enter any additional loss in the
Other Losses field. The Flexible Waveguide Loss can be deselected, which will
remove it from the loss calculation and will also remove the associated Flex
Waveguide equipment item from the BOM. In a Hot Standby configuration any
Coupler Loss cannot be edited by the user. Once any changes are made to the
Losses panel, Feeder Loss will change to User Defined Feeder Loss. If an IRFU
or RFU-A has been selected Feeder Loss will change to Maximum Feeder Loss
and will show the maximum loss for either transmit or receive, this is usually the
loss on receive at that end. The loss on transmit is incorporated into the Maximum
EIRP value.

Figure 4.17: Additional Feeder Losses in Licensed Band
If ODUs are to be mounted indoors or at the base of the tower, or the

IRFU or RFU-A has been selected, please see Long Waveguide, instead
of using this Losses option.
Secondary Feeder Loss: (PTP 820C 2+2 Only) Shows the amount of feeder loss
on the standby path (read only).
Diverse Antenna: (PTP 820C 2+0 SD Only) Select the required diverse antenna
from the drop down list.
Diverse Antenna Height: (PTP 820C 2+0 SD Only) Set the height of the diverse
antenna.
Diverse Feeder Loss: (PTP 820C 2+0 SD Only) The amount of feeder loss on the
diverse end of the link.
Tx Frequency: To change transmit frequencies at either end of the link, click on
Select.... The Select Transmit Frequencies dialog is displayed. The end of the link
which has been selected as Hi will show the higher frequencies in the band,
warnings will be displayed for 2+0 if the two Tx Frequencies at the same end of
the link are not both in the same part of the band.
If an IRFU has been selected there is also an option to change the Synthesizer
Step Size, unless the band is Lower 6 GHz, which operates on a fixed frequency
plan. At Upper 6 GHz or 7 GHz the options are 5, 50, 100, 125 and 250 kHz and at
11 GHz the options are 125 and 250 kHz, in both cases the default is 250 kHz. As
the filters are tuned to order, a wider range of frequency options are possible with
the IRFU, but may not be available from every regulator. Please check local
regulatory requirements when selecting frequencies.
Click Clear Selection to remove specific frequencies from the list, the BOM will
go back to the default ODU part numbers - before ordering make sure that these
are set to the correct part numbers by choosing the appropriate frequencies.
Link Page 163

Figure 4.18: Select Transmit Frequencies
Diversity Separation (PTP 810 Only) When 1+1 Frequency Diversity is selected
two Tx Frequency selections will be available at each end of the link. When both
frequencies have been selected the Diversity Separation will show the difference
between the two frequencies. Separations of greater than 500 MHz will not give
any further increase in the improvement factor, see Setting Diversity.
Tx Capacity Limit: (PTP 800 Only) Select the limit that must be applied to data
throughput capacity at this end of the link (Mbps). When this is changed, the
Throughput data in the Performance Summary section at the OTHER link end may
change automatically.
MMU Model: (PTP 810 only.) Select the type of MMU to use for the link.
Max Payload Bytes: (N500 only) Set the maximum packet size. Maximum value
is 1600 Bytes. Minimum value for fixed modulation mode is 64 Bytes, in adaptive
mode, the minimum may be higher than this dependent on the configured Max
and Min Modulation modes. Reducing the packet size will reduce the data rate
from the quoted data rate per mode.
Selection of MMU model is dependent on the TDM

configuration, additional modules and Ethernet throughput
required. Refer to the PTP 810 Series User Guide for further
details.

Performance Summary
This section shows how well the link is predicted to perform in response to the
selected combination of the variables, such as band, region, equipment, antenna
and height. It shows throughput performance at each end of the link. Throughput
values are displayed in either kbps or Mbps depending on the product selected.
If the predicted Throughput and Availability values fall below the required values,
they are displayed in red (Performance Summary). If they meet or exceed the
required values, they are displayed in black. In the following example, the
predicted values at North Middle School are displayed in red because they fall
below requirements, but the predicted values at Park Lane Elementary School are
displayed in black because they exceed requirements:
Figure 4.19: Performance Summary
Performance to each Site
This summary is a prediction of the Receive Power, Throughput and Availability at

each end of the link, based on the equipment and performance data entered.
Enter the required values in the data entry fields for comparison with the
predicted data.
Predicted Receive Power: The predicted receive power and
associated tolerance level at this end of the link. The tolerance is the
sum of two components, a fixed value which is dependent on the
equipment performance over temperature and a variable value which is
proportional to the amount of Excess Path Loss. When using adaptive
modulation the receive power shown is the maximum for the link, which
corresponds to the lowest selected modulation mode and Maximum
Power. If the link is operating in a higher modulation mode, the normal
operating receive power of the link may be lower, especially in the
unlicensed band or when using the ODU-B in the licensed band.
Operational Power: In licensed band when ATPC (APC) is set to
Enabled the Receive Power displayed is the Operational Power. When
ATPC (APC) is enabled the Maximum Power may be reduced depending
on the link conditions, resulting in lower measured receive powers,
which can vary over time. The value shown is a typical value at the high
end of what may be achieved. The tolerance levels shown are the same
as given for the Predicted Receive Power.
Mean throughput of the planned link in one direction:
Link Page 165

Mean IP Predicted: The mean Ethernet throughput capability,

calculated from the data entered.
Mean IP Required: Enter the required mean Ethernet throughput
capability.
% of Required IP: IP Predicted expressed as a percentage of IP
Required.
Minimum throughput of the planned link in one direction:
Min IP Required: Enter the required minimum Ethernet throughput
capability.
Min IP Availability Required (%): Enter the required minimum
availability of the link.
Min IP Availability Predicted (%): The minimum availability of the
link, calculated from the data entered, for the lowest equipment data
rate.
The Min IP Availability Predicted (%) may be higher than the

Lowest Mode Availability if the Min IP Availability Required is set
to a value greater than the data rate supported by the Minimum Mod
Mode.
If ePMP ePTP Mode, PTP 250 or Adaptive Symmetry is selected the

capacity achieved in each direction of the link is variable, depending on
the load presented. Which direction of the link will take the maximum
load is unknown therefore the values presented in the Performance to
Each Site are those of the symmetrical case. Values for the peak
throughput in a either direction can be found in Performance Details.
Operating Conditions
This option is only available when the ePMP, PTP 250, PTP 550 or PTP 820
products are selected. The throughput of these products is more dependent upon
frame size than the other PTP products and this option allows the user to select
different frame sizes and view the impact on the throughput.

Figure 4.20: Operating Conditions for PTP 250, PTP 550 or PTP 820
The throughput displayed in the Performance Summary, as well as in the

Performance Details, is for the frame size selected. The frame size options are the
standard RFC2544 sizes of 64, 128, 256, 512, 1024 and 1518 bytes. There is also
an option to select a pre-determined mixed traffic option called Tolly Mix, which is
based on the following combination of packet sizes:
55% of packets at 64 bytes
Link 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.6. The Total Path Loss and System Gain Margin are also given.
Aggregate Throughput: The sum of the Mean IP Predicted at both
ends.
Lowest Mode Availability (%): This is the availability of basic link
operation. This is equivalent to the availability of the most robust
modulation or better in both link directions.
FCC 99.95%: This is only shown when using PTP 800 or PTP 820 in
either of the FCC regulations and adaptive modulation. It shows the
modulation mode for the minimum payload capacity required by the
FCC and the two-way availability at that mode. In order to meet FCC Part
101 regulations the link must be planned to have an availability better
than 99.95% at the minimum payload when operating in adaptive mode.
System Gain Margin (dB): This is the margin in dB above which the
ratio of (mean wanted receive level) to (mean interference plus thermal
noise), or “C to (I + N)”, for the worst link direction is above the level
required for basic link operation for the most robust modulation.
Link Page 167

Free Space Path Loss (dB): The amount that the signal would be
attenuated if travelling through a vaccuum.
Mean Atmospheric Loss (dB): The amount of attenuation due to
oxygen and water in the atmosphere.
Excess Path Loss (dB): The amount of attenuation due to obstructions
in the path. If the path is completely line-of-sight, this will be zero.
Maximum Excess Path Loss (dB): (PTP 820C 2+0 SD Only) The
maximum amount of attenuation due to obstructions on the Main, Main
to Diverse or Diverse to Main paths. To achieve the full diversity
improvement shown in the Predicted Availability ensure that this value
is zero.
Total Path Loss (dB): The sum of Free Space, Mean Atmospheric and
Excess Path Loss.
Performance Summary when TDM is selected

If the equipment is PTP 300, 500, 600, 650, 670 or 700 and one or more E1 or T1
channels have been selected, then additional fields appear in the Performance
Summary section (Performance Summary with E1/T1):
E1/T1 Availability Predicted
E1/T1 Availability Required
E1/T1 Availability
E1/T1 1-way latency
For more information, see Optimizing E1 or T1 Latency.
Figure 4.21: Performance Summary with E1/T1
If the equipment is PTP 810 or PTP 820G then additional fields appear in the
Performance Summary section (Performance Summary with TDM for PTP 810):
STM-1 Carried (PTP 810 Only)

E1 Carried
TDM Availability Required
TDM Availability Predicted
If the Regulation selected is either FCC or Canada (or T1 TDM Type has been
selected for PTP 820G), then E1 will be replaced by T1. The Availability Required is
used in the same way as the Min IP Availability Required. The Availability Predicted
is the two way availability of the link.
When operating with a fixed modulation mode the Availability Predicted for the
TDM circuits will be the same as the Link Availability.
Figure 4.22: Performance Summary with TDM for PTP 810
Link Summary additional information for PTP 800, PTP 810 or PTP 820
If the equipment is PTP 800, PTP 810 or PTP 820, additional information is
available via the icon. Select the icon to view a new window showing the
detailed breakdown of the availability calculations, see Detailed Availability
Information (ITU Model). This allows the information to be viewed during planning
without having to produce a proposal report.
Link Page 169

Figure 4.23: Detailed Availability Information (ITU Model)
This window shows detailed information for Link Availability when in fixed
modulation mode or for Lowest Mode Availability when Adaptive Modulation has
been selected. When the ITU prediction model has been selected, see Availability,
the parameters are as displayed in Detailed Availability Information (ITU Model)
and described below:
dN/dH not exceeded for 1% of time: Point refractivity gradient in the lowest
65m of the atmosphere not exceeded for 1% of an average year. This data is
provided in 1.5 deg grid form by the ITU and the value is a bilinear interpolation
for the mid point of the path.
Area roughness 110 x 110 km: the standard deviation of terrain heights (m)
within a 110 x 110 km area.
Geoclimatic Factor: Calculated from the point refractivity gradient and area
roughness according to ITU-R P530-12.
Fade Occurrence Factor (P0): The intercept of the deep-fading distribution with
the percentage of time-axis for multipath fading. This parameter is dependent on
the Geoclimatic Factor, path length, path inclination, frequency and altitude of
lower antenna, calculated as given in ITU-R P530-12.

Path Inclination: Absolute difference in antenna height above mean sea level
(m) divided by path length (km), given in mrad.
SD Improvement Factor: Only visible if Spatial Diversity has been selected. The
improvement factor is based on the diversity spacing and calculated in
accordance with ITU-R P530-13. This factor is limited at 200, as the conditions
required to achieve a better improvement factor will already achieve 100%
availability, see Setting Diversity.
FD Improvement Factor: Only visible if Frequency Diversity has been selected.
It is a similar parameter to the SD Improvement Factor and is based on the
diversity separation. It has the same range of values, see Setting Diversity.
Value of K Exceeded for 99.9% (ke): This value is taken from ITU-R P.530
Figure 2, the value of ke exceeded for approximately 99.9% of the worst month in
a continental temperature climate and is often referred to as “Worst Earth
Curvature”. The impact of this value on the terrain height is shown by the grey
line on the path profile (Profile with Trees).
Excess Path Loss at K = ke: This value shows the amount of excess loss that
will occur on the link during the time when the K value drops to that shown above.
This may occur for up to 0.1% of the time, but is not taken into account in the
availability calculations. Links which require at least 99.9% availability should
ensure that this value is 0 dB, by selecting appropriate antenna heights to give
sufficient clearance.
0.01% Rain rate: Calculated using ITU-R P837-5, which uses a matrix of rain
values for the globe with a 1.25 degree resolution. These values are bi-linearly
interpolated for the Latitude and Longitude of the center of the path.
Rain Availability: The availability of the given rain rate with the system gain
margin calculated using ITU-R P530-12.
Rain Unavailability: The amount of time the link is predicted to be unavailable
due to rain.
Annual 1-way Availability: The annual availability due to clear air multipath
effects in a single direction, shown for each end of the link. This also accounts for
any obstructions on the path.
Annual 2-way Availability: The sum of both 1-way unavailabilities, expressed
as availability.
Annual 2-way Unavailability: The amount of time the link is predicted to be
unavailable due to multipath effects.
Annual 2-way Availability Including Rain: The sum of the Rain Unavailability
and the Annual 2-way Unavailability, expressed as availability.
Annual 2-way Unavailability Including Rain: The total time the link is
predicted to be unavailable.
When using the Vigants - Barnett prediction model the first five parameters are
replaced by the following terms, for further information on the Vigants - Barnett
model see Availability :
Terrain Roughness: Standard deviation of terrain height along the path profile,
excluding the ends of the path.
Link Page 171

Climatic Factor: Derived from the atmospheric conditions maps for the mid point
of the path.
C Factor: Calculated from the Terrain Roughness and the Climatic Factor.
Temperature: The temperature is taken from the ESATEMP data. This data is
provided in 1.5 deg grid form by the ITU and the value is a bilinear interpolation
for the mid point of the path.
Performance Details
This section contains more detail about the predicted performance of the link. The
data can either be displayed in chart or tabular form.
Charts
The following charts show the variability in percentage of time availability with
capacity, for each direction in the link. When the cursor is moved over the chart
the area is highlighted in blue and the chart is annotated with throughput,
availability (given as a percentage) and unavailability (given as a unit of time).
The throughput given is the maximum throughput at that availability.
Figure 4.24: Performance Charts
When Dual Payload is enabled the availability shown is the sum of Receive
time in Mode for all single and dual payloads with a Max IP Throughput
greater than or equal to the given capacity level.
If ePMP, PTP 250, or PTP 820 are selected the capacity shown in both the charts
and the table is for the given frame size selected.
If ePMP Enhanced PTP Mode, PTP 250 or Adaptive Symmetry is selected the
capacity achieved in each direction of the link is variable, depending on the load
presented. The charts cannot predict the load for each direction of the link and
therefore present data for two conditions, see Performance Charts for Adaptive
Symmetry.

When traffic is only being sent in one direction the other direction has no
load on it and a peak throughput can be achieved in a single direction at a
given time.
When one direction of the link is saturated the maximum throughput in the
other direction balances that load and provides a symmetrical throughput in
each direction, for identical link conditions. In this case the values shown in
the chart correlate with the values shown in the Performance Summary
section.
Figure 4.25: Performance Charts for Adaptive Symmetry
- high capacity, which can only be achieved in this direction assuming there
is no load in the other direction.
- symmetrical capacity, which can be achieved assuming a saturated load

in the other direction. This capacity can be achieved simultaneously with the
equivalent load shown on the opposite direction of the link.
Link Page 173

Table
Figure 4.26: Performance Details
Common Details
MCS: (ePMP Only) The Modulation Coding Scheme Number

Mode: The modulation technique used.
Code Rate: The code rate for the specified Mode (not available for PTP 820, PTP
450 or PTP 450i).
Profile: (PTP 820 Only) The profile number of the modulation mode.
MIMO Type: (PTP 450 and 450i Only) The MIMO method used.
Payloads: (ePMP, PTP 300, 400, 500, 600, 650 or 700) Indicates whether the
payload mode is Single or Dual.
Multiplier: (PTP 450 and 450i Only) Indicates the relative capacity capability of
the different modes.
Max. Aggregate IP Throughput (Mbps): The maximum aggregate throughput
achievable (sum of both directions). This field is automatically adjusted for the
range of the link being studied.
STM-1 Carried: This row is only displayed if the equipment is PTP 810.
E1/T1 Carried: This row is only displayed if the equipment is PTP 600, PTP 650,
PTP 700, PTP 810 or PTP 820G and one or more E1 or T1 channels have been
selected. It indicates the number of E1 or T1 channels supported in each
modulation mode. For PTP 600, PTP 650 or PTP 700 it is set to “Timing” for those
modulation modes that are below the Lowest Telecom Mode selected in the
Equipment section, for more information, see Optimizing E1 or T1 Latency.

Performance to each end
Max. IP Throughput (Mbps): The maximum user throughput achievable. For

modulation modes below Lowest Ethernet Mode this value will be set to zero
and no contribution from these modulation modes will be included in the ** Mean
IP Predicted**.
Fade Margin (dB): The margin available to each end in the specified Mode.
Mode Availability (%): The percentage of time that the data throughput rate
shown for each end will be available.
Receive Time in Mode (%):The percentage of time used to receive data in the
specified Mode.
When PTP 250 or Adaptive Symmetry is selected the values shown in the
Performance to each end section of the table assume that there is no load in
the opposite direction of the link.
Bill of Materials for Link
LINKPlanner automatically calculates the Bill of Materials (BOM) for the required
components of the planned link. The link BOM contains the list of part numbers
and associated quantities for the link. Optional items can be added to the list. The
link BOM can be saved as a CSV or Excel file by clicking View in Spreadsheet .
Part numbers for PTP 650L are not included in the BOM. Replace PTP
650S parts with equivalent PTP 650L part numbers and add capacity
license key if appropriate. Ignore any range upgrade license key for PTP
650S, this is not required for PTP 650L.
To view the link BOM, open the Link page and scroll down to the ” Bill of Materials
for Link” section.
Figure 4.27: Bill of Materials for Link
P/N: The Cambium part number. If the component is not supplied by Cambium,
this is set to ‘(no part number)’.
Description: Description of the components.
Qty: Quantity required.
Link Page 175

Notes: By default this displays information about certain items, such as whether
they are obsolete, or to prompt for additional required information, such as
frequencies for the IRFU. This field can be edited to allow additional information to
be added to the item. The default text is returned if the edited text is deleted.
When information is displayed in the Notes field, items will only be aggregated at
the Project Level BOM if the Notes field contains identical information as well as
being the same part number.
A warning triangle is displayed on the far left of a line if additional information is
required in the Notes field or in the configuration. A star denotes optional extras
which have been added to the automatic BOM items and a star with a warning
triangle is an optional extra which requires additional information to be included in
the note.
Figure 4.28: Bill of Materials Icons
To add additional items to the BOM, click New Extra . A list of

optional extras for the given product will be displayed. The list of items will vary
depending upon the product selected. To add items to the BOM tick the box next
to each item required and click OK. The items will appear in the main list, where
the quantity can be adjusted by selecting the number in the Qty column and
adjusting as required. To delete optional items from the BOM list, highlight the
items and click Delete Extra . A star denotes optional extras
which have been added to the automatic BOM items.

Figure 4.29: Bill of Materials Optional Extras
The groups and extras will vary depending on the chosen product.
The individual items at the top of the list give quick access to the most popular
optional extras. To access more options, expand the list topics.
Accessories: Additional accessories.
All Indoor: This option is only available for the PTP 800 and PTP 820 series and
allows upgrade kits and field replaceable items to be specified for IRFU and RFU-A
links.
Antennas: (PTP820 Only) Additional PTP 800 antenna options.
Cable, Accessories & Spares: This allows items such as additional cable,
optical splitters, PTP Sync, E1/T1 splitters etc. to be added to the order.
Capacity Keys: PTP 810 capacity key licenses and upgrades.
Capacity Licenses: PTP 300, PTP 500 and PTP 650 license upgrades.
cnReach Radios: N500 alternative radios.
Comsearch: Allows FCC Frequency Coordination or Protection Services to be
added to the order.
GPS Synchronization: (PTP 450 Only). Optional GPS Modules can be included
with the order.
Installation & Mounting: Optional installation, grounding and mounting kits can
be included with the order.
Kits: PTP 650 alternative ODU and power supply kits.
Licenses: PTP 650 additional license options.
License Keys: PTP 820 license keys and capacity upgrades.
Link Page 177

Lightning Protection: Lightning protection options.

Link Protection: This option is only available for the PTP 800 and PTP 820 series
and allows additional cabling and splitter options to be specified for a 1+1
Protected Link.
Long Waveguide: This option is only available for the PTP 800 series and allows
additional options for the mounting components when using long feeder runs
either for the Long Waveguide option or for IRFU.
Modem Base Modules: PTP 810 base modules.
Modem Expansion I/O Modules: PTP 810 expansion modules.
Modem Spare Modules: PTP 810 spare modules.
NMS: PTP 820 Network Management System parts
Power: This allows AC/DC power supplies and country specific mains leads and
PIDU to be included with the order.
Quick Deploy Positioner: This allows the parts for the Quick Deploy Positioner
to be added to PTP 450i, PTP 650 and PTP700.
Security: There is a range of different encryption options available, depending
upon the product selected.
Switch: A range of switch options.
Warranty & Support: Additional warranty options are available to extend the
warranty by 1, 2 or 4 years. Also annual PTP software support contracts are
available, depending upon the number of links required.
To filter the list of optional extras, enter a part number or description in the Filter
field.
For instructions on how to view and save the BOM for the entire project,
see Bill of Materials for Project.
Viewing & saving the link BOM file in MS Excel
To view the link BOM in Excel, click View in Spreadsheet while viewing the
link BOM. Once in the spreadsheet the file can be saved as normal.
All numeric only part numbers consist of 11 digits, if the number

displayed is only 10 digits the part number should start with a zero.

Advanced Features
To improve the performance of links additional features are available in certain

PTP products.
For PTP 300, 500, 600, 650, 670 or 700
Optimize E1 or T1 latency, see Optimizing E1 or T1 Latency
For PTP 300, 500, 600, 650, 670 or 700
Use TDD Synchronization, see Setting TDD Synchronization. For further
background information giving an overview of Time Division Duplex, see TDD
Overview or for an overview of TDD Synchronization, see TDD
Synchronization Overview.
For PTP 800, 810 or 820
Enable Hot Standby Protection, including Spatial Diversity, see Setting Hot
Standby Protection (1+1)
Use 2+0 Antenna Sharing, see Setting 2+0 Antenna Sharing
For PTP 800, 810 or 820
Installing IRFUs (PTP 800i/810i) or RFU-As (PTP 820i) indoor, see Long
Waveguide
For PTP 800
Installing ODUs indoor or at the base of the tower, see Long Waveguide
For all PTP products (except ePMP, N500, PTP 450, PTP 450i, PTP 550 and PTP
820S)
Use Diversity, including Reflections, see Setting Diversity
Optimizing E1 or T1 Latency
When a number of E1 or T1 channels are selected in the Link Description and

Equipment section, the LINKPlanner is able to predict the latency for those
channels. The latency is displayed in the Link Summary section of the
Performance Summary.
The latency depends on a number of factors which may be out of the user’s
control, such as the link range and radar detection requirements. It also depends
on the number of telecoms channels selected, the channel Bandwidth, and the
Lowest Telecoms Mode. By adjusting these values, it may be possible to improve
the latency.
The Lowest Telecoms Mode or Lowest TDM Mode selection determines which
modulation modes will be allowed to carry telecoms data. Lower modulation
modes will only carry timing information. The product will then optimize the
latency for that modulation mode. For more information, see the section titled
“Telecoms Circuits” or “TDM bridging” in the appropriate product User Guide,
which can be downloaded from https://support.cambiumnetworks.com/files.
In the LINKPlanner, the Lowest Telecoms Mode selection box lists the modulation
modes and their ability to carry the selected telecoms payload. If the mode would
Advanced Features 179

be unable to carry that payload, it displays “Timing”. Otherwise it displays the

selected channels.
Figure 4.30: Lowest Telecoms Mode
In this example, 16QAM 0.87 Sngl is the first modulation mode capable of
carrying the 2 T1 channels - the lower modes can only carry timing information.
However, by selecting a higher modulation mode, the latency may be reduced
(potentially at the expense of the E1/T1 Availability, if the selected modulation
mode does not have a high enough availability)
When E1/T1 is selected, the Performance Details display will also gain an extra
row which indicates whether the mode will be carrying E1/T1 payloads, or timing
data only.
Setting TDD Synchronization
TDD synchronization settings involve adjustment of an individual link in the

Equipment Pane of a link and of the global parameters in the TDD Sync node in
the navigation tree. For a more detailed understanding of TDD Synchronization,
see TDD Synchronization Overview.
When TDD synchronization is enabled for a link, the link will

show zero data rate until a valid set of global options are
selected in the TDD Synchronization List and a warning will be
displayed in the TDD Synchonrization Sub-Panel

Figure 4.31: TDD Synchronization Error Message
The process for setting TDD synchronization is:

1. Enable TDD synchronization in the Equipment section of the Link page, as
described in Link Description and Equipment.
The TDD Synchronization Sub-Panel is displayed. Use it to display and adjust
the TDD settings for the individual link.
Figure 4.32: TDD Synchronization
Phase 1 End: In a hub and spoke arrangement there are several links
emanating from one tower. Each link on that tower normally needs to be set
to the same phase. In a simple network this will be setting each Phase 1 End
to the hub end. If there is more than one hub in a network then it may be
necessary to have some towers set for all of the links to be Phase 2 at the
hub or Phase 1 at the outstations. This is achieved by setting the Phase 1
end to the opposite ends of the links from the hub end.
2. Set the Maximum Burst Duration and Frame Duration, as described in TDD
TDD Overview
Cambium PTP unlicensed band links consist of a Master unit and a Slave unit. The
links use a duplexing scheme known as Time Division Duplex (TDD). To activate
TDD Synchronization, see Setting TDD Synchronization.
TDD operates by only allowing one end of the link to transmit at any one time.
This allows both link directions to operate on the same radio frequency. This
differs from Frequency Division Duplex (FDD), where each end can transmit and
receive simultaneously but this requires the two directions to operate on different
frequencies, thereby increasing the spectral requirements.
TDD operates in a cyclic fashion, with the transmissions alternating between the
two ends. The cycle of events is as follows:
1. Master transmits a burst
2. A delay occurs as the Master burst travels over the air
3. Slave receives the burst

4. A delay as the Slave processes the burst

5. The slave transmits a burst
6. A delay as the slave burst travels over the air
7. Master receives the burst
8. A delay as the Master processes the burst
9. Master transmits a burst
One cycle is called a Frame. The cycle period is called the Frame Duration. This is
shown in Basic TDD Frame. For purposes of illustration, the delays in this diagram
have been exaggerated.
Figure 4.33: Basic TDD Frame
The size of the burst depends on the configuration of TDM mode, IP mode and link
symmetry.
TDM Mode
If the PTP link is carrying TDM traffic (E1s or T1s), it is desirable to keep the burst
as short as possible in order to minimize latency. However, with shorter bursts, a
greater proportion of the frame is taken up by the radio propagation delay and the
burst processing delay thus reducing throughput. So, in TDM mode, the PTP link
reduces the burst size as far as possible whilst still maintaining the throughput
required for the configured number of E1s and T1s. The result is that burst sizes
are greater for longer links.
IP Mode
If the PTP link is carrying IP traffic only, it is often desirable to increase throughput
at the expense of latency. In IP mode therefore, the PTP link maximizes burst size.
This makes the propagation delay and processing delay proportionately smaller
making the frame more efficient.

Symmetry
The system can be configured to give more or less of the frame to a particular
direction. Possible values are:
Symmetric: Equal burst size for both link directions. Each link direction has
the same maximum throughput.
Adaptive: This mode is only available in IP mode. The size of the burst
effectively adapts to the traffic being offered from the network and is
independent of the size of the burst in the other link direction. As the offered
traffic level increases in a given direction, the size of the burst increases in
that direction in order to increase frame efficiency and therefore throughput.
As the offered traffic level decreases in a given direction, so the size of the
burst in that direction decreases. This allows the other link direction to take a
greater proportion of the frame if required.
2:1 (PTP 600, PTP 650 only): Master Tx Burst is twice the size of Slave Tx
Burst. Maximum throughput in the direction towards the Slave is twice the
Maximum throughput in the direction towards the Master.
3:1 (PTP 300/500 only): Master Tx Burst is three times the size of Slave Tx
Burst. Maximum throughput in the direction towards the Slave is three times
the Maximum throughput in the direction towards the Master.
1:2 (PTP 600, PTP 650 only): Slave Tx Burst is twice the size of Master Tx
Burst. Maximum throughput in the direction towards the Master is twice the
Maximum throughput in the direction towards the Slave.
1:3 (PTP 300/500 only): Slave Tx Burst is three times the size of Master Tx
Burst. Maximum throughput in the direction towards the Master is three
times the Maximum throughput in the direction towards the Slave.
Summary
The frame duration is dependent on:

Burst size.
Propagation delay (link length).
System processing delays.
The burst size is dependent on configuration:
In TDM mode, the burst sizes are minimized as far as possible in order to
reduce latency.
In IP mode, the burst sizes are maximized in order to increase throughput. As
processing delay and propagation delay are fixed (for a given link length),
larger bursts are more efficient as a greater proportion of the frame is being
used to carry data.
TDD Synchronization Overview
The performance of any radio is dependent on the level of electromagnetic

interference to which it is subjected. This is also the case for the PTP Outdoor

Units (ODUs).
PTP ODUs are installed as pairs to form a Point to Point radio link. In an ideal radio
environment, any individual ODU will receive transmissions only from the paired
ODU at the other end of the link. However, when multiple links are installed, an
ODU may also be subjected to interference from the transmission of an ODU
which is part of another link. This is depicted in Interference Between ODUs,
which shows an example concentrating specifically on ODU A as an interferer.
Both ODU C and ODU D are subjected to interference from ODU A.
Figure 4.34: Interference Between ODUs
Interference between units on the same mast is the most problematic due to their
close proximity. The problem becomes worse when the angular separation
between links (see Separation of PTP 600 Units on a Mast) is small. This can be
alleviated by using the following techniques:
Increasing the separation between the victim’s receive frequency and the
interferer’s transmit frequency. With limited spectrum, this becomes more
difficult with increasing numbers of links.
Increasing the physical separation between the interferer and the victim.
Separation of PTP 600 Units on a Mast vertically separated on a mast.
Reducing the transmit power of the interfering radio. However, this may
affect the performance of the interferers own link in the direction away from
the common mast.

Figure 4.35: Separation of PTP 600 Units on a Mast
The techniques for minimizing interference on a common mast are described in

documents PTP 600 Series Deploying Collocated Units and PTP 300/500 Series
Planning Guide for Collocation. If these techniques do not reduce interference
sufficiently, then TDD synchronization should be considered.
TDD synchronization works by aligning the frames of all links in the network
thereby eliminating interference between those ODUs which are configured to
operate on the same phase of the TDD cycle. To understand this, it is first useful
to consider the TDD frames of the two links shown in Separation of PTP 600 Units
on a Mast with synchronization disabled.
Unsynchronized Links
When the frames of two links are unsynchronized, the transmission from one ODU
may overlap the receive frame of any another ODU. Unsynchronized Frames
shows the frames of the two links “A to B” and “C to D”. The diagram focuses on
ODU A as the interferer. It can be seen that the transmission from ODU A is
overlapping the receive period of both ODU C and ODU D. As well as the frames
not being aligned, the frame duration of link “C to D” is longer than that of link “A
to B”. This is because the propagation delay of this link is longer. This means that
the size of the overlap will vary from frame to frame. This is illustrated by the
overlap period with ODU D Rx being longer in the first frame than in the second
frame.

Figure 4.36: Unsynchronized Frames
Synchronized Links
The primary advantage of TDD synchronization is that the network can be

configured such that the transmit burst of an ODU does not overlap the receive
burst of a collocated ODU. This eliminates the most problematic interference
mechanism.
Taking the same example pair of links, Synchronized Frames shows the two links
with TDD synchronization enabled. The start of each frame now occurs at the
same point in time. This is achieved by the use of a GPS synchronization box
which injects a pulse into the Master ODU every second. One GPS synchronization
box is required for each Master ODU and the pulse occurs at the same point in
time for every GPS synchronization unit in the network. The Master ODU then
offsets the center of its frame relative to the pulse by a configurable delay. The
intention of this delay is to allow the Master to be configured to transmit on either
Phase 1 (which is when the pulse aligns with the center of the Master transmit
burst) or Phase 2 (which is when the center of the Master transmit burst is
delayed by half the frame duration relative to the pulse). The default is for
Masters to be on Phase 1 which is suited to the common case of collocating
Master ODUs at “hub” sites.
In Synchronized Frames, collocated ODUs A and C transmit on Phase 1, i.e. the 1
pulse per second aligns with the center of the transmit burst. The remote ODUs B
and D transmit on Phase 2, 180 degrees out of phase with ODU A and C.
The result of TDD synchronization is that the receive period of ODU C never
overlaps with the transmission burst from the collocated ODU A - and vice versa.
Also, the receive period of remote ODU B never overlaps with the transmission

burst from remote ODU D - and vice versa. However, the receive period of the
remote ODU D still overlaps with the transmission from ODU A. In fact, they are
now perfectly aligned. This highlights the key result of TDD synchronization which
is that half of the network interference mechanisms are eliminated, or more
precisely, the interference between units operating on the same phase of the TDD
cycle is eliminated.
In order to eliminate interference between units which are on the same phase but
which are NOT collocated, the propagation delay of the victim link and the
interference path needs to be considered. This leads to the optimization of three
parameters:
Burst Duration
Frame Duration
slaveTxRxGap
Burst Duration and Frame Duration are self explanatory and are shown in
Synchronized Frames. The parameter slaveRxTxGap is also shown in
Synchronized Frames and allows the frames of shorter links to stretch to that of
the longest link in order to keep a common network frame duration. This
highlights a key disadvantage of TDD synchronization in that the efficiency of
shorter links reduce to those of the longer links. Also note that adaptive frame
structures are no longer possible. In fact, only symmetrical frame structures are
supported when TDD synchronization is enabled.
Optimization of these parameters as well as the configuration of phase using Link
Planner is discussed in Setting TDD Synchronization.

Figure 4.37: Synchronized Frames
Setting Hot Standby Protection (1+1)
Hot Standby is available on PTP 800, PTP 810 and PTP 820 links and involves
configuring two units at each end of the link to operate as primary and secondary
(standby) units. For a more detailed understanding of 1+1 Hot Standby, see the
appropriate product User Guide.
Hot Standby can be enabled as described in Link Description and Equipment.
Once enabled, the Project Navigation Tree shows the link node and then the four
paths as sub-headings to the main link, as shown in Navigation Tree for Protected
(1+1) link.

Figure 4.38: Navigation Tree for Protected (1+1) link
The link node gives access only to the Link Description, Equipment Selection and
Bill of Materials aspects of the link configuration, see Link Node Information for
Protected (1+1) link. To access all other sections of the Link Page select one of the
four paths, e.g. Primary to Primary.
Figure 4.39: Link Node Information for Protected (1+1) link

Hot Standby Configuration at Each End
Select the required path for the protected link. In addition to the normal
parameters as described in Link Description and Equipment, links operating Hot
Standby have the following additional attribute displayed:
Antenna Configuration: There are up to 4 options which can be
selected to match the possible configurations for Hot Standby when
using an ODU Product or PTP 820.
Common Antenna - Symmetric Coupling
Common Antenna - Asymmetric Coupling - default setting
Redundant Antennas - PTP 800 Only
Spatial Diversity, see Setting Diversity
There are 5 options which can be selected to match the possible
configurations for Hot Standby when using an IRFU product.
Equal Splitter - default setting
Equal Splitter MHSB Ready
Unequal Splitter
Unequal Splitter MHSB Ready
Spatial Diversity, see Setting Diversity
There are 3 options which can be selected to match the possible
configurations for Hot Standby when using a PTP 820i product.
Common Antenna - Asymmetric Coupling - default setting
Spatial Diversity (Split End), see Setting Diversity
Spatial Diversity (Standard), see Setting Diversity
The primary and secondary parameters at each end can be configured as
described in Configuration at Each End, by selecting the following paths:
Primary to Primary
Primary to Secondary
Secondary to Primary
Secondary to Secondary
Although the parameters can be configured through either the primary or
secondary interface, some parameters are common to both configurations at the
same end of the link. Any changes made to either primary or secondary
configuration will automatically be reflected in the other configuration at that end
of the link.
Antenna Type: If one of the common antenna protection options has
been selected this value will be the same for both primary and
secondary. If the redundant antennas or spatial diversity option have
been selected then a different antenna can be chosen for primary and
secondary. If using an FCC regulation Cat B, Cat B1 or Cat B2 antennas

can be used as a receive only diverse antenna in locations where a Cat

A primary antenna is required. In such locations these antennas must
not be used for transmit, see PTP 800 Series User Guide or PTP 810
Series User Guide for further details on the correct way to commission
the PTP 800 and PTP 810 modems for use with these antennas.
Antenna Height: If one of the common antenna protection options has
been selected this value will be the same for both primary and
secondary. If the redundant antennas or spatial diversity option have
been selected then a different antenna height can be chosen for
primary and secondary.
Diversity Spacing: This field is only shown when the Antenna
Configuration is set to Spatial Diversity and it shows the difference
in height between the Primary and Secondary antennas. Improvement
in availability will only occur when this value is greater than zero, see
Setting Diversity.
Feeder Loss: This field will incorporate the coupler loss in addition to
any waveguide loss. Any User Defined additional loss which has been
included will be the same for both primary and secondary remote
antennas for any of the common antenna protection options, but can be
different for primary and secondary if the redundant antennas or spatial
diversity option have been selected. The symmetric coupler will have
the same loss for both primary and secondary, whereas the asymmetric
coupler has a lower loss for the primary and higher loss for the
secondary. For the IRFU the losses will always be defined by the more
complex Losses spreadsheet as described in Long Waveguide, as the
losses are not the same for both transmit and receive.
Maximum EIRP: The EIRP will often be different for the primary and
secondary, in the majority of cases the primary will have the higher
value. If the secondary has a higher value than the primary, a warning
will be shown on the display, as this might violate the terms of the
license.
The IRFU and RFU-A in Standard configuration only transmit through the
Primary Antenna and Feeder System, therefore for Spatial Diversity
using an IRFU or RFU-A (Standard), the EIRP is calculated using the
Primary Antenna Gain and Feeder Losses. The Secondary Maximum
EIRP and Maximum Power will be the same as for the Primary and there
are no separate User Limits for the Secondary. The receive path uses
the Secondary Antenna Gain and Feeder Losses.
Maximum Power: This field can be set independently for primary and
secondary, unless using IRFU or RFU-A (Standard) Spatial Diversity or
PTP 810.
PTP 810 only supports a single transmit power setting during

installation. It also supports a setting for coupler loss, which when using
a common antenna is the difference in coupler loss between the primary

and secondary path. For Spatial Diversity the coupler loss is any
additional loss due to lower antenna gain and feeder loss on the
secondary path. The coupler loss is shown on the Installation Report.
The Secondary Maximum EIRP and Maximum Power are calculated from
the Primary Maximum Power and there are no separate User Limits for
the Secondary.
Tx Frequency: This value will always be the same for primary and
secondary.
Tx Capacity Limit: PTP 800 Only. This field can be set independently
for primary and secondary.
Link MMU Model: PTP 810 Only. This value will always be the same for
primary and secondary.
Interference: This value will always be the same for primary and
secondary.
Hot Standby Bill of Materials
The Bill of Materials is displayed at the link node level and shows the full set of
equipment required for both the primary and secondary units. For PTP 800, Hot
Standby can be operated with either in-band or out-of-band management. If
out-of-band management is required then additional items may be required to
make up a full set of equipment, which can be selected via the New Extras
icon, see Bill of Materials Optional Extras.
Hot Standby Performance Summary
The performance summary information is shown separately for each path and can
be accessed by selecting the appropriate path, for example Primary to
Secondary, from the navigation tree. The required performance parameters can
be set independently for each path and are defined in the usual way, see
Performance Summary.
If the predicted performance of the primary to primary path is below requirements,
then the main link node will be displayed in red. If the performance of any of the
other paths is below requirements then the associated sub-path in the navigation
tree will be shown in red, but will not affect the annotation of the link node, the
map display or the link table . If a particular path is not considered relevant to the
performance of the link, it can be “switched off” by setting the following:
Mean IP Required to 0.1 Mbps
Min IP Availability Required to 0.0000%
For PTP 800 and PTP 810 Spatial Diversity improvement is only applied to the
lowest configured modulation mode, therefore it will always be included in the
Link Summary parameter Lowest Mode Availability. It will usually also be
included in the Min IP Availability Predicted, however if the Min IP Required
is greater than that supported by the Minimum Mod Mode, there will be no

spatial diversity improvement included in the Min IP Availability Predicted. If

IRFU or RFU-A (Standard) are selected with Spatial Diversity the Secondary to
Secondary performance is not relevant as the transmit path is always through
the primary antenna.
Hot Standby Reports
There are two levels of report available in Hot Standby. By default a standard
report is produced, which concentrates on the performance of the primary to
primary link or a detailed report can be produced which details all four paths.
When the protected link option is selected for the first time by a user the following
message is displayed allowing the user to choose the type of report.
Figure 4.40: Detailed Reports Information Message
The type of reports can be changed at any time by clicking Tools, Options,
Reports and then selecting or deselecting the Generate detailed reports
option.

Figure 4.41: Detailed Reports Selection
The proposal and installation reports are created for a given link, not path, in the
usual way, see Creating Reports. The level of detail presented will depend upon
the detailed reports selection and which product is selected. The standard reports
only show performance information for the primary to primary path. If a common
antenna has been selected, or the link is PTP 810, only one set of installation
notes will be produced for each end of the link, any parameters which might be
different between the primary and secondary units will be clearly specified. This
includes the predicted receive power at both the primary and secondary units at
one end from the primary unit at the other end. If redundant antennas or spatial
diversity have been selected separate installation notes will be produced for the
primary and secondary units for PTP 800, as several parameters are likely to be
different. PTP 810 will still show a single section for each end, but include all
parameters which might be different.
The detailed reports contain both installation and performance information for
each of the path combinations, with the significant changes outlined in the
following sections.
Detailed Proposal Report

The throughput information for each end of the link and the link summary
information is shown for each of the paths.

Figure 4.42: Proposal Report Performance Information for Protected (1+1) Link
For both sets of performance information the primary to primary notation refers to
the left end to right end of the link, in this example Wood Farm to West Tower.
For the Performance to West Tower the information is shown for the perfomance
received at West Tower when:
Primary to Primary - both Wood Farm and West Tower are set to primary.
Primary to Secondary - Wood Farm is set to primary and West Tower is
receiving a signal on its secondary unit.
Secondary to Primary - Wood Farm is transmitting on its secondary unit,
whilst West Tower is still receiving on its primary unit.
Secondary to Secondary - both Wood Farm and West Tower are using their
secondary units
Detailed Installation Report

The initial sections of the report (link summary, path profile and link

configuration) are shown for the primary to primary path. For PTP 800 the site
installation notes are given for both the primary and secondary units at each end
of the link, however for PTP 810 it is given as a single report for each end, showing
any difference in primary and secondary parameters as required. The BNC
Target Voltage and Predicted Receive Power are given for both the primary
and secondary units with the other end of the link operating on primary.
If the values are required to verify the secondary to secondary path, then the
Predicted Receive Power can be estimated quite closely for the common
antenna configuration. The BNC Target Voltage can be derived from the
received signal level using the RSSI voltage table given in PTP 800 Series User
Guide or PTP 810 Series User Guide. Assuming that the same power level is used
for both primary and secondary then the impact will be as follows:
Symmetric Couplers - no change in predicted receiver power
Asymmetric Couplers - the predicted receive power will drop by 5.4 dB
compared with the secondary receive power level.
If the transmit powers are different for primary and secondary then the offset will
have to be adjusted according to the difference. Equally if different antennas are
used for primary and secondary the predicted receive power for the secondary to
secondary path will be changed (with respect to the primary to primary path) by
the sum of the difference in antenna gains at each end of the link.
For both PTP 800 and PTP 810 the performance information is given for all four
paths, in a similar manner to the detailed proposal report.
Setting 2+0 Antenna Sharing
2+0 antenna sharing is available on PTP 800, PTP 810 and PTP 820 links. How to
configure 2+0 depends on the product and whether an outdoor or indoor RFU is
used:
PTP 800, PTP 810, PTP 820S and PTP 820G require two RFUs at each end of
the link to operate either through a common coupler to a single antenna or a
dual polar antenna to provide two parallel links between two sites.
2+0 Co-Polar with an IRFU combines the two paths through an additional
circulator to a single antenna, removing the loss of the coupler.
PTP 820C requires a single RFU and either an OMT or splitter with a single
polarity antenna.
For a more detailed understanding of 2+0 Antenna Sharing, see the appropriate
product User Guide.
2+0 antenna sharing using outdoor RFUs is not available for some
bands, regulations, T/R spacings or bandwidths, for PTP 800 and PTP
810, see the product User Guide for further information. For PTP 820
ensure that the two pairs of frequencies are in the same sub-band.
2+0 antenna sharing can be enabled as described in Link Description and
Equipment, for 2+0 Co-Polar (ACCP), 2+0 Cross-Polar (ACAP) and 2+0 XPIC (CCDP)

(PTP 810 or PTP 820 Only). For PTP 800i with IRFU the only option is 2+0 Co-Polar,
all 3 options are available for PTP 810i with IRFU, with the 2+0 Cross-Polar and
2+0 XPIC using dual polar antennas. Once enabled, the Project Navigation Tree
expands to show a link node and its two associated links Link A and Link B. The
2+0 Cross-Polar is shown in Navigation Tree for 2+0 Cross-Polar link.
Figure 4.43: Navigation Tree for 2+0 Cross-Polar link
It is differentiated from the 2+0 Co-Polar, which is shown in Navigation Tree for
2+0 Co-Polar link, by the ‘x’ between the parallel lines in the link icon.
Figure 4.44: Navigation Tree for 2+0 Co-Polar link
The 2+0 XPIC configuration, which is shown in Navigation Tree for 2+0 XPIC link,
is differentiated by the ‘XPIC’ between the parallel lines in the link icon.

Figure 4.45: Navigation Tree for 2+0 XPIC link
For PTP 800 the link node gives access only to the Link Description, Region and
Equipment Selection and Bill of Materials aspects of the link configuration, see
Link Node Information for PTP 800 2+0. PTP 810 and PTP 820 also display all
Equipment parameters, the Performance Summary and Performance Details for
the aggregated link, see Link Node Information for PTP 810 2+0. For PTP 810 and
PTP 820G the number of STM-1 (PTP 810 Only) and E1 or T1 circuits is configured
for Link A and Link B at the link node level and cannot be changed at the lower
levels. Click either Link A or Link B to configure the individual path settings.
Figure 4.46: Link Node Information for PTP 800 2+0

Figure 4.47: Link Node Information for PTP 810 2+0
2+0 Equipment Configuration
The Region and Equipment Selection information is repeated from the link node
configuration for all products. The Link Type and TDM Configuration (PTP 810
and PTP 820G only) cannot be changed at this level, however the other
parameters can be changed and any changes will be reflected in the other link.
For PTP 800 click either Link A or Link B to set up the product section of the
equipment configuration, for PTP 810 and PTP 820 this is also repeated from the
link node configuration. For PTP 800 the product configuration settings can all be
changed independently for Link A and Link B with the exception of the
Polarization, which is shared for the 2+0 Co-Polar option and is reversed from Link
A to Link B when 2+0 Cross-Polar is selected. For PTP 810 and PTP 820 the
product configuration information is all shared, with the following exception:
Polarization, which operates the same as for PTP 800, also being reversed
from Link A to Link B when 2+0 XPIC is selected.
For PTP 810 and PTP 820 2+0 XPIC only supports bandwidths of 28 MHz or
greater. For PTP 810 2+0 XPIC also only supports Fixed Modulation Modes of 64
QAM or higher. XPIC is only valid on LOS links, if the link has any Excess Path Loss
the Throughput and Availability predictions will be set to zero. The link must be
LOS in order to achieve the required polarization discrimination for XPIC operation.

Obstructions: Linkplanner User Guide, Release 4.8.2

Uploaded by

Copyright:

Available Formats

Obstructions: Linkplanner User Guide, Release 4.8.2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Obstructions: Linkplanner User Guide, Release 4.8.2

Uploaded by

Copyright:

Available Formats

LINKPlanner User Guide, Release 4.8.

Figure 3.42: Profile Visualization Chart

Figure 3.43: Profile Editor

Figure 3.44: Profile Updated With Tree Obstructions (in green)

Adding new points

92 Chapter 3. Using LINKPlanner

Figure 3.45: Adding a Profile Point

Editing multiple points

Figure 3.46: Setting a Constant Gradient

Copy a Path Profile

 Open the Profile Editor and click

Pasting a Path Profile

 Open the Profile Editor and click

94 Chapter 3. Using LINKPlanner

Figure 3.47: Path Profile Units

Editing a Profile as a Spreadsheet

Link Profile Adjustment Examples

Figure 3.48: Original path profile

 Verifying a High Point Using a Survey

Figure 3.49: Adjusted path profile

Verifying a Link End Using a Map and Google Earth

96 Chapter 3. Using LINKPlanner

Figure 3.50: Unadjusted profile near antenna site

The first 0.1 km of this link must be examined in more detail.

Figure 3.51: Map of Addislade

 Just in front of the antenna - a building and some bushes, estimated

Figure 3.52: Obstructions and higher ground near Addislade

98 Chapter 3. Using LINKPlanner

Verifying a Link End Using a Survey

Figure 3.54: GPS Calibration Point

We calibrate the GPS at this point.

100 Chapter 3. Using LINKPlanner

Figure 3.55: Using a ruler to estimate height

We record the estimated antenna height: 10m.

Figure 3.56: Results of site survey at Addislade

Figure 3.57: Profile updated with site survey results

102 Chapter 3. Using LINKPlanner

Verifying a High Point Using a Map

Figure 3.58: Unadjusted profile near high point

Figure 3.59: Map of Hp1

The path profile height 156.5 m at range 1.061 km is probably correct.

Figure 3.60: Estimated obstruction height near Hp1

Verifying a High Point Using a Survey

104 Chapter 3. Using LINKPlanner

 Map, path profile, Google Earth(TM) aerial photo

Figure 3.61: GPS Calibration Point near Hp1

We calibrate the GPS at this point.

Figure 3.62: Profile updated with Hp1 survey results

106 Chapter 3. Using LINKPlanner

Bill of Materials for Project

Bill of Materials for Project 107

Figure 3.63: Bill of Materials for Project

Viewing & saving the project BOM file

108 Chapter 3. Using LINKPlanner

All numeric only part numbers consist of 11 digits, if the number

Bill of Materials for Project 109

110 Chapter 3. Using LINKPlanner

 Subscriber Module Antennas

Open the Profile Editor and click

Open the Profile Editor and click

Verifying a High Point Using a Survey

Just in front of the antenna - a building and some bushes, estimated

Map, path profile, Google Earth(TM) aerial photo

Subscriber Module Antennas