LINKPlanner v4.8.7 Now Available

A new release of the LINKPlanner is available from https://support.cambiumnetworks.com/files/linkplanner  

The Windows version of this release is now a Cambium signed executable.

The key features of 4.8.7 are:

New or changed features

If you have the LINKPlanner email address bookmarked please update your address books with the new address.

  • PMP 450 family
    • Increased PMP 450m max EIRP levels for downlink beamforming

See the Knowledge Base article for more details on the changes to the PMP 450m EIRP limits, https://community.cambiumnetworks.com/t5/LINKPlanner/Understanding-PMP-450m-EIRP-limits/m-p/95872#M24

  • Added Device Type parameters to PTP 450i and PTP 450b Installation Reports

These parameters are to determine whether the device is to operate in BHM/BHS or in Multipoint mode as an SM.

  • PTP 820
    • PTP 820G
      • Added Ethernet configuration selection for:
        • Single Ethernet MC-ABC
        • Multiple Ethernet with LAG
        • Multiple Ethernet without LAG
      • Added header compression

This now gives equivalent options in the PTP 820G to the PTP 820C

  • PTP 820S and PTP 820C
    • Changed cable drops to fiber for antenna heights > 90 meters (295 feet)
    • Updated management cable requirements on protected links
  • PTP 820C
    • Added 4+0 Single Ethernet
    • Removed 2+0 and 4+0 Multiple Ethernet for antenna heights > 90 meters (295 feet) (old files may open with errors)
    • Removed 2+2 Multiple Ethernet (old files may open with errors)
  • PTP 820C HP
    • Changed default radios to NON-MIMO, which provides another Ethernet port
    • Added 4+0 Single Ethernet
    • Removed 2+2 Multiple Ethernet (old files may open with errors)
    • Added second fiber drop for Multiple Ethernet

Please see the Knowledge Base article on Cable drops and Ethernet Configurations for PTP 820 for more guidance on the above configurations, http://community.cambiumnetworks.com/t5/LINKPlanner/Cable-drops-and-Ethernet-Configurations-for-PTP-820/m-p/95876#M25

 

  • Added 6 GHz RadioWave antenna conversion kits into Optional Extras
  • cnReach
    • Added 700 MHz band to PMP mode
    • Where allowed by regulatory, provided AP Tx Lo option

In a similar manner to PTP some regulatory bands allow the AP and SM to be configured to be either Hi or Lo. The channel frequencies selected in the Channel Plan will always be the Hi values but will be allocated to the AP or SM depending on the Hi end setting.

  • Added T/R = Unpaired to numerous bands in Channel Plans program

The “Unpaired” setting configures the same frequency to both the AP and SM as in conventional TDD PMP networks and is specific variant of the “Any” T/R spacing. When the T/R is set to Unpaired a normal channel plan can be used to allocate the channels to the APs in the network. If the intention is to use the same Tx/Rx frequency, then it is recommended to use the Unpaired setting.

  • Added AP and SM frequency selection for T/R = Any

When the T/R option is configured for “Any” the Channel plan functionality cannot be used, instead the individual frequencies for the AP and SM are configured directly at the AP using a similar transmit frequency selection window to the one used on a PTP link.

image001.png

 

When the Select… button is chosen a new Select Transmit Frequencies window is displayed. A warning will be shown if the frequencies selected do not match the Hi/Lo selection. Either correct in the Transmit Frequency window or accept the frequencies and then change the Hi/Lo selection. If the frequencies selected are the same then a reminder will be shown to use the “Unpaired” option, but the frequencies can still be configured on the AP if required.

 image002.png

  • Replaced Wideband omni antenna with band-specific omni antennas
  • Enforced antenna polarization selections between PTP ends and AP/SM

This ensures that Vertically polarized antennas cannot be configured at one end of the link and Horizontally polarized antennas at the other resulting in a cross-polarization loss on the link.

  • PTP 650
    • Added Cambium Sync (CMM5) support using 01-46

Although the PTP 650 product is now obsolete it can now be connected to the CMM5 Cambium Sync unit if required.

Bug Fixes

  • PMP 450m
    • Updated Mu-MIMO grouping algorithm for Rel 16.0

This changes the maximum number of groups being formed in low bandwidths and low or high Downlink Data ratios.

  • Clarified Flood Test results page headings to show LINKPlanner emulates DL and UL Only flood tests and not bi-directional.

The product supports the ability to run bi-directional or single direction flood tests. LINKPlanner only predicts the performance from single direction flood tests. When comparing the performance between the product and LINKPlanner check whether there is any background traffic on the radio in the opposite direction which will reduce the measured performance in comparison with the predicted results.

  • Changed regulatory implementation for the following PMP 450 family bands:
    • Added Pakistan at 5.8 GHz
    • Added Nigeria at 5.1, 5.2 and 5.8 GHz
    • Updated Mexico in 4.9 and 5.4 GHz
    • Corrected upper frequency limit for 3.6 GHz India
    • Australia – removed from 3.6 GHz and added 15 MHz bandwidth at 3.5 GHz
    • Corrected lower band edge for 3.5 GHz ETSI from 3400 to 3410 MHz
    • Removed Indonesia from 3.5 GHz band
  • Corrected PTP 550 2+0 bandwidth selection options

Ensures that the correct bandwidth options are being offered for all combinations of different frequency bands, split-frequency bands and single frequency bands

  • Corrected PTP Equipment Templates to support custom antennas
  • PTP 820G unit redundancy removed spatial diversity and corrected BOM fiber adapter quantities

Spatial diversity is not supported with the PTP 820G or PTP 820i 2x1+0 Unit Redundancy configuration on the product and has been removed from LINKPlanner. This release increases the number of fiber adapters for Line Protection Mode (Optical) and Optical Splitter Mode and Fiber 1+1 splitters for Optical Splitter Mode.

  • Corrected CMM5 equipment aggregation on PTP 670/700 in network level BOM

Releases 4.8.5 and 4.8.6 aggregated the CMM5 component parts at the network level BOM for PTP 670 and PTP 700, when this is not appropriate across different PTP End points. This has been corrected in this release.

  • Corrected PMP BOM Estimator cnReach SM Equipment in 400 – 470 MHz bands

Previous releases were incorrectly showing 900 MHz radios and 900 MHz antenna kits in the BOM Estimator for PMP subscriber modules. This has been corrected to show the correct radios and available antenna kits for the frequency band selected.

  • Removed Channel Plan parameters from PMP Equipment Templates to prevent channel plans from being over-written

Previous versions of LINKPlanner showed the Channel Plan options in the PMP Equipment Template which allowed a common channel plan to be applied, but if the channel plan was then updated to allocate the actual channels to each AP and then the PMP Equipment Template is reapplied, the channel plan was over-written (even if it was left blank). The Channel Plan is not expected to be a common parameter for all APs in a network and has been removed from the template.

  • Added ability for negative heights to be added with new terrain points in the path profile to support areas below Average Mean Sea Level
  • Improved centering of dialog boxes onto parent LINKPlanner window

All pop-up windows will now appear over the LINKPlanner parent window, whichever screen that is displayed on.

  • Removed MMS Hop Offset selection from licensed band cnReach

This is not used in licensed band only for 900 MHz ISM, but it may cause an error message when opening an old project. This error message can safely be ignored.

When updating to this version I can no longer see my Mapped network drives through the Linkplanner if I want to set a default path for my Template. Oddly the Windows File Explorer shows that the network drives are still there. I am downgrading back to 4.8.4 as there seems to be no way around this.

What version of Windows are you using? It works as expected for me in Windows 8 and 10.

Thanks,


Andy

It turns out, running as admin will remove the mapped Network Drives. I ran without admin and it appears that my Network Drives now show up. Thanks